return for code block group based transmissions

专利摘要:
several characteristics related to a single bit ack / nack return for cbg based transmissions in a communication system are described. in one aspect, a base station can transmit to a eu a set of cbgs of a tb including a first subset of cbgs and a second subset of cbgs, the first subset of cbgs being transmitted over at least partially punctured resources. the base station can receive an ack / nack from the eu based on the transmitted set of cbgs, and retransmit to the eu one of the complete set of cbgs or the first subset of cbgs based on the ack / nack. in one respect, a eu can decode the set of cbgs received from the base station, transmit ack / nack feedback based on a decoding result, and receive, based on the transmitted ack / nack feedback, a retransmission from either complete set of cbgs, or the first subset of cbgs.
公开号:BR112019020124A2
申请号:R112019020124
申请日:2018-03-29
公开日:2020-05-05
发明作者:Jiang Jing；Sun Jing
申请人:Qualcomm Inc；
IPC主号:

专利说明:

RETURN FOR CODE BLOCK GROUP BASED TRANSMISSIONS
CROSS REFERENCE TO RELATED APPLICATION (S) [0001] This order claims the benefit of US Provisional Order Serial No. 62 / 481,089, entitled SINGLE BIT RETURN FOR CBG BASED TRANSMISSIONS filed on April 3, 2017, and US Patent Application No. 15 / 939,165, entitled RETORNO FOR CODEBLOCK GROUP BASED TRANSMISSIONS and filed on March 28, 2018, which are expressly incorporated herein by reference in their entirety.
FUNDAMENTALS
Field [0002] The present disclosure generally relates to communications systems and, more particularly, to methods and devices related to single bit acknowledgment (ACK) / negative acknowledgment (NACK) for transmissions based on code block group (CBG).
Fundamentals [0003] Wireless communication systems are widely used to provide various telecommunications services, such as telephony, video, data, messaging and transmissions. Typical wireless communication systems can employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access systems (CDMA), time division multiple access systems (TDMA), multiple division access systems
Petition 870190096214, of 26/09/2019, p. 6/124
2/85 frequency (FDMA), orthogonal frequency division multiple access systems (OFDMA), single carrier frequency division multiple access systems (SCFDMA) and time division code division multiple access systems in sync with time division (TD-SCDMA).
[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate at a municipal, national, regional, and even global level. An exemplary telecommunication standard is 5G Novo Rádio (NR). 5G NR is part of an evolution of continuous mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet the new requirements associated with latency, reliability, security, scalability (for example, with the Internet of Things (IoT)), and other requirements. Some aspects of the 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements in the 5G NR technology. These improvements may also apply to other multi-access technologies and the telecommunications standards that use those technologies.
SUMMARY [0005] The following is a simplified summary of one or more aspects, in order to provide a basic understanding of such aspects. This summary is not a broad overview of all aspects covered, and is not intended to identify key or critical elements of all aspects or to outline the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified way
Petition 870190096214, of 26/09/2019, p. 7/124
3/85 as a prelude to the more detailed description that is presented later.
[0006] The various characteristics related to the support of a single bit ACK / NACK for CBG-based transmissions in a communication system are described. In one aspect of the invention, a method, a computer-readable medium, and an apparatus are provided. The apparatus, for example, a base station, can be configured to transmit, to a user device (UE), a set of code block groups (CBGs) including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs being transmitted over resources at least partially punctured. For example, resource punctuation / preemption can refer to an operation in which a resource occupied by the information / data corresponding to a type of communication, for example, an ongoing Enhanced Mobile Broadband (eMBB) communication, can be punctured / deprecated to carry information / data for another type of communication, for example, a Low Latency and High Reliability (URLLC) type transmission. The device can be further configured to receive an ACK / NACK return from the UE based on the set of transmitted CBGs. The device can be additionally configured to retransmit, based on the ACK / NACK feedback received, one of the set of CBGs or the first subset of CBGs. In some configurations, the device can be additionally configured to transmit a CBG confirmation including information indicating one or more CBGs that have been transmitted over
Petition 870190096214, of 26/09/2019, p. 8/124
4/85 punctured / partially punctured features.
[0007] In one aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus, for example, a UE, can be configured to decode a set of CBGs received from a base station, the set of CBGs including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs having been transmitted on resources at least partially punctured. The device can be further configured to transmit an ACK / NACK return based on decoding to the base station. The device can be further configured to receive from the base station, based on the transmitted ACK / NACK feedback, a retransmission of an element of the CBG set or the first subset of CBGs.
[0008] For the realization of the above and related purposes, the one or more aspects comprise the characteristics described below and particularly highlighted in the claims. The following description and the accompanying drawings present in detail certain characteristics illustrating one or more aspects. These resources are indicative, however, of just a few of the various ways in which the principles of various aspects can be employed, and this description is intended to include all of these aspects and their equivalents.
BRIEF DESCRIPTION OF THE DRAWINGS [0009] Figure 1 is a diagram that illustrates an example of a wireless communications system and an access network.
Petition 870190096214, of 26/09/2019, p. 9/124
5/85 [0010] Figures 2A, 2B, 2C, and 2D are diagrams that illustrate examples of a DL frame structure, DL channels within the DL frame structure, a UL frame structure, and UL channels within the frame structure UL, respectively.
[0011] Figure 3 is a diagram illustrating an example of a base station and an UE in an access network.
[0012] Figure 4 illustrates communications between a base station and an UE in an exemplary communication system that supports dynamic resource sharing for Ultra-Reliable and Low-Latency Communications (URLLC) and Advanced Mobile Broadband (eMBB) communications, in an exemplary scenario where a retransmission is triggered by an exemplary ACK return.
[0013] Figure 5 illustrates signal exchange between the base station and the UE of the communication system of figure 4 in an exemplary scenario where a retransmission is triggered by an exemplary NACK return.
[0014] Figure 6 illustrates a specific example of signaling exchange between the base station and the UE and processing in yet another scenario where a retransmission is triggered by a NACK return.
[0015] Figure 7 illustrates signal exchange between the base station and the UE of the communication system of figure 4 in an exemplary scenario where an ACK to NACK error occurs, for example, in which a transmitted ACK is interpreted incorrectly by base station as a NACK due to a receive / decode error.
[0016] Figure 8 illustrates another example that shows the signaling between the base station and the UE, where
Petition 870190096214, of 26/09/2019, p. 12/104
6/85 an ACK to NACK error occurs, for example, where a NACK
transmitted is interpreted incorrectly by the station base how an ACK because one mistake in reception / decoding. [0017] | Figure 9 is a flow chart in a method in communication without thread of a base station. [0018] | Figure 10 is a flow chart in a method in
wireless communication from an UE.
[0019] Figure 11 is a conceptual data flow diagram illustrating the data flow between different media / components in an exemplary device.
[0020] Figure 12 is a diagram that illustrates an example of a hardware implementation for a device that employs a processing system.
[0021] Figure 13 is a conceptual data flow diagram illustrating the data flow between different media / components in another exemplary device.
[0022] Figure 14 is a diagram that illustrates an example of a hardware implementation for a device that employs a processing system.
DETAILED DESCRIPTION [0023] The detailed description presented below in connection with the accompanying drawings is intended to be a description of various configurations and is not intended to represent the only configurations in which the concepts described here can be practiced. The detailed description includes specific details for the purpose of providing a complete understanding of various concepts. However, it will be evident to those skilled in the art that these concepts can be practiced without these specific details. In
Petition 870190096214, of 26/09/2019, p. 12/114
7/85 some well-known cases, structures and components are shown in the form of a block diagram in order to avoid obscuring such concepts.
[0024] Various aspects of telecommunications systems will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the accompanying drawings by various circuit blocks, components, processes, algorithms, etc. (collectively referred to as elements). These elements can be implemented using electronic hardware, computer software, or any combination of these. Whether these elements are implemented as hardware or software depends on the specific application and design limitations imposed on the global system.
[0025] As an example, an element, or any portion of an element, or any combination of the elements can be implemented as a processing system, which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems in a chip (SoC), baseband processors, field programmable port arrangements (FPGA), programmable logic devices (PLD), state machines, closed logic, discrete hardware circuits, and other suitable hardware configured to run the various features described throughout
Petition 870190096214, of 26/09/2019, p. 12/124
8/85 of this disclosure. One or more processors in the processing system can run the software. Software should be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, execution tasks, procedures, functions, etc., be referred to as software, firmware, middleware, microcode, hardware description language, or other.
[0026] Consequently, in one or more exemplary modalities, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, functions can be stored in or encoded as one or more instructions or code in a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available media that can be accessed by a computer. As an example, and not as a limitation, such computer-readable media may comprise random access memory (RAM), read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, storage on magnetic disk, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer .
Petition 870190096214, of 26/09/2019, p. 12/13
9/85 [0027] Figure 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wide area wireless network (WWAN) ) includes base stations 102, UEs 104, and an Evolved Packet Core (EPC) 160. Base stations 102 can include macro cells (high power cell base station) and / or small cells (low power cell base station). Macro cells include base stations. Small cells include femto cells, pico cells, and micro cells.
[0028] Base stations 102 (collectively referred to as the Evolved Mobile Telecommunications System (UMTS), Terrestrial Radio Access Network interface (E-UTRAN)) with EPC 160 through 132 return transport links (for example, the interface Sl). In addition to other functions, base stations 102 can perform one or more of the following functions: user data transfer, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (for example, handover , dual connectivity), inter-cell interference coordination, connection and release establishment, load balancing, non-access layer (NAS) distribution messages, NAS node selection, synchronization, radio access network (RAN) sharing, service multicast and multimedia broadcast (MBMS), equipment and subscriber traces, RAN information management (RIM), paging, positioning and delivery of warning messages. Base stations 102 can communicate directly or indirectly (for example, through EPC 160) with each other over
Petition 870190096214, of 26/09/2019, p. 12/144
10/85 return transport channel links 134 (for example, interface X2). The return transport channel link 134 can be wired or wireless.
[0029] Base stations 102 can communicate wirelessly with UEs 104. Each base station 102 can provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For For example, small cell 102 'may have a coverage area 110' that overlaps coverage area 110 of one or more macro base stations 102. A network, which includes both small cells and macro cells, may be known as a heterogeneous network. A heterogeneous network can also include Domestic Evolved Node (eNB) (HeNBs), which can provide services to a restricted group, known as a closed subscriber group (CSG). Communication links 120 between base stations 102 and UEs 104 may include uplink (UL) transmissions (also referred to as reverse link) from UE 104 to base station 102 and / or downlink (DL) transmissions ( also referred to as a direct link) from a base station 102 to a UE 104. Communications links 120 can use multiple input and multiple output antenna (MIMO) technology, including spatial multiplexing, beam formation, and / or diversity transmission. Communication links can be through one or more carriers. Base stations 102 / UEs 104 can use spectrum up to Y MHz (for example, 5, 10, 15, 20, 100 MHz) of bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (carriers of component X) used for transmission
Petition 870190096214, of 26/09/2019, p. 12/154
11/85 in each direction. The carriers may or may not be adjacent to each other. Carrier allocation can be asymmetric in relation to DL and UL (for example, more or less vehicles can be allocated to DL than to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier can be referred to as a primary cell (cell) and a secondary component carrier can be referred to as a secondary cell (cell).
[0030] The wireless communications system may also include a Wi-Fi Access Point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz frequency spectrum not licensed. When communicating on an unlicensed frequency spectrum, STAs 152 / AP 150 can perform a clean channel assessment (CCA) prior to communication, in order to determine if the channel is available.
[0031] Small cell 102 'can operate on a licensed and / or unlicensed frequency spectrum. When operating on an unlicensed frequency spectrum, small cell 102 'can employ NR and use the same unlicensed 5 GHz frequency spectrum as used by the AP Wí-Fí 150. Small cell 102', using NR on a unlicensed frequency spectrum, can intensify coverage and / or increase the capacity of the access network.
[0032] The gNóB (gNB) 180 can operate at millimeter wave frequencies (mmW) and / or frequencies
Petition 870190096214, of 26/09/2019, p. 12/164
12/85 almost mmW in communication with UE 104. When gNB 180 operates at mmW or near mmW frequencies, gNB 180 can be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RE in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in the band can be referred to as a millimeter wave. Almost mmW can extend downwards at a frequency of 3 GHz, with a wavelength of 100 mm. The superhigh frequency band (SHE) extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW / almost mmW radio frequency band have extremely high loss of travel and a short range. The mmW 180 base station can use beamform 184 with UE 104 to compensate for extremely high, short-range travel loss.
[0033] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a service gateway 166, a Multicast Broadcast Multimedia Service Gateway (MBMS) 168, a Broadcast and Multicast Service Center ( BM-SC) 170, and a Packet Data Network Gateway (PDN) 172. MME 162 may be in communication with a Domestic Subscriber Server (HSS) 174. MME 162 is the control node that processes signaling between UEs 104 and EPC 160. Generally, MME 162 provides carrier and connection management. All user Internet Protocol (IP) packets are transferred via Service Gateway 166, which in turn is connected to Gateway PDN 172. Gateway PDN 172 provides assignment of UE IP addresses, as well as other
Petition 870190096214, of 26/09/2019, p. 12/174
13/85 functions. The Gateway PDN 172 and BM-SC 170 are linked to IP Services 176. IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS Streaming Service (PSS), and / or others IP services. The BM-SC 170 can provide functions for provisioning and delivering MBMS user service. The BM-SC 170 can serve as an entry point for transmitting MBMS from content provider of, can be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and can be used to program MBMS transmissions. The MBMS 168 Gateway can be used to distribute MBMS traffic to base stations 102 belonging to a Multicast and Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start / stop) and to collect billing information related to eMBMS.
[0034] The base station can also be referred to as a gNB, node B, evolved Node B (eNB), an access point, a base transceiver station, a base radio station, a radio transceiver, a transceiver function, a basic service set (BSS), a set of extended services (ESS), or some other appropriate terminology, without loss of generality. Base station 102 provides an access point for EPC 160 for a UE 104. Examples of UEs 104 include a cell phone, a smartphone, a login protocol (SIP) phone, a laptop, a personal digital assistant ( PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a
Petition 870190096214, of 26/09/2019, p. 12/184
14/85 digital audio player (e.g. MP3 player), camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, toaster, or any similar operating device. Some of the UEs 104 can be referred to as loT devices (for example, parking meter, gas pump, toaster, vehicles, etc.). UE 104 can also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless device wireless communications, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other terminology proper.
[0035] Referring again to Figure 1, in certain respects, base station 180 can be configured to transmit, to a UE (for example, UE 104), a set of CBGs including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs being transmitted over at least partially punctured resources, receive an ACK / NACK return from the UE based on the transmitted set of CBGs, and retransmit one of the set of CBGs or the first subset of CBGs to the UE based on the ACK / NACK return received (198). UE 104 can be configured to decode the set of CBGs received from the base station, transmit an ACK / NACK return to the base station
Petition 870190096214, of 26/09/2019, p. 12/194
15/85 based on the decoding, and receive, based on the transmitted ACK / NACK return, a retransmission of one of the set of CBGs or the first subset of CBGs from the base station (198). Various features and techniques disclosed here support low latency operations and the efficient use of radiolink resources, for example, with support for dynamic resource sharing between URLLC and eMBB communications.
[0036] Figure 2A is a diagram 200 illustrating an example of a DL frame structure. Figure 2B is a diagram 230 illustrating an example of channels within the DL frame structure. Figure 2C is a diagram 250 that illustrates an example of a UL frame structure. Figure 2D is a diagram 280 that illustrates an example of channels within the UL frame structure. Other wireless communication technologies may have a different frame structure and / or different channels. One frame (10 ms) can be divided into 10 subframes of equal size. Each subframe can include two consecutive time partitions. A resource grid can be used to represent the two time partitions, each time partition including one or more concurrent time blocks of resources (RBS) (also referred to as physical RBs (PRBs)). The resource grid is divided into several resource elements (REs). For a normal cyclic prefix, an RB contains 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols (for DL, OFDM symbols; for UL, SC-FDMA symbols) in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB contains 12 consecutive subcarriers in the domain of
Petition 870190096214, of 26/09/2019, p. 12/204
16/85 frequency and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.
[0037] As illustrated in Figure 2A, some of the REs carry DL (pilot) reference signals (DLRS) for channel estimation in the UE. DL-RS can include cell-specific reference signals (CRS) (sometimes also called common RS), UE-specific reference signals (UE-RS), and channel status information reference signals (CSI-RS ). Figure 2A illustrates CRS for antenna ports 0, 1, 2, and 3 (indicated as RO, Rl, R2, and R3, respectively), UE-RS for antenna port 5 (indicated as R5), and CSI-RS for antenna port 15 (indicated as R). Figure 2B illustrates an example of several channels within a DL subframe of a frame. The physical control format indicator (PCFICH) channel is within the 0 symbol of partition 0, and carries a control format indicator (CFI) that indicates whether the physical downlink control channel (PDCCH) occupies 1, 2, or 3 symbols (Figure 2B illustrates a PDCCH that occupies 3 symbols). The PDCCH carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. A UE can be configured with an enhanced UE-specific PDCCH (ePDCCH) which also carries DCI. The ePDCCH can have 2, 4 or 8 RB pairs (Figure 2B shows two RB pairs, each subset including a RB pair). The physical hybrid auto-repeat request (ARQ) indicator channel (HARQ) (PHICH) is also within the
Petition 870190096214, of 26/09/2019, p. 12/21
17/85 symbol 0 of partition 0 and carries the HARQ indicator (HI) which indicates HARQ negative feedback (ACK) / ACK (NACK) based on the shared physical channel (PUSCH). The main synchronization channel (PSCH) can be within the symbol 6 of partition 0 within subframes 0 and 5 of a frame. The PSCH carries a main synchronization signal (PSS) which is used by a UE to determine subframe / symbol timing and a physical layer identity. The secondary synchronization channel (SSCH) can be within the symbol 5 of partition 0 within subframes 0 and 5 of a frame. The SSCH carries a secondary synchronization signal (SSS) that is used by a UE to determine a physical layer cell identity and radio frame timing group number. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the DL-RS locations mentioned above. The physical broadcast channel (PBCH), which carries a master information block (MIB), can be logically grouped with the PSCH and SSCH to form a synchronization signal block (SS). The MIB provides a number of RBs in the DL system bandwidth, a PHICH configuration, and a system frame number (SEN). The shared physical downlink channel (PDSCH) carries user data, performs non-transmissible system information through PBCH such as system information blocks (SIBS), and paging messages.
[0038] As shown in Figure 2C, some of the REs carry demodulation reference signals
Petition 870190096214, of 26/09/2019, p. 12/22
18/85 (DM-RS) for channel estimation at the base station. The UE can also transmit sound reference signals (SRS) at the last symbol of a subframe. The SRS can have a comb structure, and a UE can transmit SRS on one of the combs. The SRS can be used by a base station for channel quality estimation to activate frequency-dependent programming at UL. Figure 2D illustrates an example of several channels within a UL subframe of a frame. A physical random access channel (PRACH) can be within one or more subframes within a frame based on the PRACH configuration. The PRACH can include six consecutive RB pairs within a subframe. The PRACH allows the UE to perform initial system access and achieve UL synchronization. A physical uplink control channel (PUCCH) can be located at the edges of the UL system bandwidth. 0 PUCCH carries uplink control (UCI) information, such as scheduling requests, a channel quality indicator (CQI), a pre-coding matrix indicator (PMI), a rating indicator (RI), and return ACK / NACK HARQ. The PUSCH carries data, and can additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.
[0039] Figure 3 is a block diagram of a base station 310 in communication with a UE 350 on an access network. In DL, EPC 160 IP packets can be provided to a 375 controller / processor. The 375 controller / processor implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control layer (RRC), and layer 2 contains a
Petition 870190096214, of 26/09/2019, p. 12/23
19/85 packet data convergence protocol layer (PDCP), a radiolink control layer (RLC), and a medium access control layer (MAC). The 375 controller / processor provides the RRC layer functionality associated with broadcasting system information (for example, MIB, SIBs), RRC connection control (for example, RRC connection paging, RRC connection establishment, RRC connection modification , and RRC connection release), mobility of radio access technology (RAT), and measurement configuration for EU measurement reports; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity checking), and delivery support functions; RLC layer functionality associated with the transfer of data units in upper layer packets (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs , and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logic channels and transport channels, multiplexing MAC SDUs in transport blocks (TBS), demultiplexing MAC TBUs from TB, programming data information, correcting errors through HARQ , priority handling, and logic channel prioritization.
[0040] The transmit processor (TX) 316 and the receive processor (RX) 370 implement layer functionality associated with various signal processing functions. Layer 1, which includes a physical layer (PHY), can
Petition 870190096214, of 26/09/2019, p. 12/24
20/85 include error detection in transport channels, direct error correction (FEC) encoding / decoding of transport channels, interleaving, rate combining, mapping over physical channels, modulating / demodulating physical channels, and processing of MIMO antenna. The TX 316 processor handles mapping to signal constellations based on various modulation schemes (for example, binary phase shift switching (BPSK), quadrature phase shift switching (QPSK), M phase shift switching (M -PSK), amplitude modulation in M quadrature (M-QAM)). The coded and modulated symbols can then be divided into parallel streams. Each fraction can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (for example, pilot) in the time and / or frequency domain, and then combined together using a Fast Inverse Fourier Transform. (IFFT) to produce a physical channel carrying a stream of OFDM symbols in the time domain. The OFDM stream is spatially pre-coded to produce multiple spatial streams. Channel estimates from a 374 channel estimator can be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimation can be derived from a reference signal and / or channel condition return transmitted by the UE 350. Each spatial flow can then be provided to a different antenna 320 via a separate transmitter 318TX. Each 318TX transmitter can modulate an ER carrier with a respective spatial flow for transmission.
Petition 870190096214, of 26/09/2019, p. 12/25
21/85 [0041] In the UE 350, each 354RX receiver receives a signal through its respective antenna 352. Each 354RX receiver retrieves modulated information about an RE carrier and provides the information for the receiving (RX) 356 processor. 0 processor TX 368 and 356 RX processor implement layer 1 functionality associated with various signal processing functions. The RX 356 processor can perform spatial processing on the information to retrieve any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined by the RX 356 processor into a single OFDM symbol stream. The RX 356 processor then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (EFT). The frequency domain signal comprises a separate stream of OFDM symbols for each OFDM signal subcarrier. The symbols on each subcarrier, and the reference signal, are retrieved and demodulated by determining the most likely signal constellation points transmitted by base station 310. These smooth decisions can be based on channel estimates calculated by the channel estimator 358. The smooth decisions are then decoded and deinterleaved to retrieve the data and control signals that were originally transmitted by base station 310 over the physical channel. The control data and signals are then provided to the controller / processor 359, which implements both layer 3 and layer 2 functionality.
[0042] The 359 controller / processor can be associated with a 360 memory that stores the codes and
Petition 870190096214, of 26/09/2019, p. 12/26
22/85 program data. 360 memory can be referred to as a computer-readable medium. In UL, the 359 controller / processor provides demultiplexing between transport and logic channels, packet reassembly, decryption, header decompression, and control signal processing to retrieve IP packets from EPC 160. The 359 controller / processor is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0043] Similar to the functionality described in connection with DL transmission by base station 310, the 359 controller / processor provides the RRC layer functionality associated with acquiring system information (eg, MIB, SIBs), RRC connections, and reports measurement; PDCP layer functionality associated with compression / decompression header, and security (encryption, decryption, integrity protection, integrity checking); RLC layer functionality associated with the transfer of top layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logic channels and transport channels, multiplexing MAC SDUs over TB, demultiplexing MAC SDUs from TBs, programming information reporting, error correction through HARQ, priority handling , and logic channel prioritization.
[0044] Channel estimates obtained by a 358 channel estimator from a reference signal
Petition 870190096214, of 26/09/2019, p. 12/27
23/85 or feedback transmitted by base station 310 can be used by the TX 368 processor to select the appropriate modulation and encoding schemes, and to facilitate spatial processing. The spatial streams generated by the TX 368 processor can be provided with a different antenna 352 via separate transmitters 354TX. Each 354TX transmitter can modulate an RF carrier with a corresponding spatial flow for transmission.
[0045] The UL transmission is processed at base station 310 in a manner similar to that described in connection with the receiver function in the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX retrieves modulated information about an RF carrier and provides the information for an RX 370 processor.
[0045] The 375 controller / processor can be associated with a 376 memory that stores the program codes and data. Memory 376 can be referred to as a computer-readable medium. At UL, the 375 controller / processor provides demultiplexing between transport and logic channels, packet reassembly, decryption, header decompression, control signal processing to retrieve IP packets from the UE 350. IP packets from the controller / processor 375 can be provided for EPC 160. The controller / processor 375 is also responsible for error detection, using an ACK and / or NACK protocol to support HARQ operations.
[0044] As described here, the 359/375 controller / processor supports HARQ operations
Petition 870190096214, of 26/09/2019, p. 12/28
24/85 at the transport block (TB) level and / or CBG level where a device can request retransmission of a partial TB, for example, one or more CBGs of a TB, or complete TB, in which case all TB CBGs can be retransmitted. According to several characteristics described here, in some configurations, the retransmission of the complete TB from base station 310 can be triggered by a NACK from the UE 350, while the retransmission of a subset of CBGs from a previously transmitted set of CBGs can be triggered by an ACK from the UE 350.
[0044] LTE and NR systems support many different applications that have strict latency and / or reliability requirements such as URLLC, and others, such as eMBB. In some NR systems, for example, resource sharing between dynamic URLLC and eMBB can be supported, for example, with an indicator channel, through which an indication of eMBB resources being punctured for use in the transmission of URLLC data can be provided . For example, a resource occupied by an eMBB communication in progress can be punctured / avoided for a URLLC type transmission. In such cases, a device, for example, a base station, can provide an indication, for example, on a downlink control channel such as the PDCCH, indicating the punctured resources for transporting URLLC traffic to a UE that may be available. waiting for data of type eMBB in the resource (s) of eMBB. punctured / avoided. The indication regarding the impacted resources of the eMBB can facilitate the demodulation and decoding of the UE of the current transmission and subsequent retransmissions of the impacted eMBB data.
Petition 870190096214, of 26/09/2019, p. 12/29
25/85 [0049] When puncturing occurs, the UE can probably fail to decode one or more CBGs corresponding to the punctured resources, for example, CBGs that are transmitted over the punctured resources. A CBG retransmission level scheme can allow the retransmission of failed CBGs instead of retransmission of an entire TB that included CBGs. Such an approach is more efficient in the sense that other successfully decoded CBGs, for example, that have passed a cyclic redundancy check (CRC), are not retransmitted. However, with such an approach, a CBG level ACK / NACK Return may be required, that is, one ACK / NACK bit per CBG may be needed to indicate which CBG is properly decoded and which is not. Thus, if burst interference corrupts one or more code blocks (CBs) of a CBG, the CBG can be retransmitted. Although ideally, a CB-level retransmission is desirable, but the CBG concept provides a balance between ACK / NACK return overhead and retransmission efficiency.
[0050] In one approach, CBG-based transmission with single-bit ACK / NACK HARQ feedback can be supported. This approach may have, for example, one or more of the following characteristics: CBG-based (re) -transmission may be permitted only for the same TB as a HARQ process, CBGs for which a retransmission is required may include all CBs / CBGs of a TB, regardless of the size of the TB, in which case the UE can report a single ACK HARQ bit to the TB, CBGs for which retransmission is required may include one or more
Petition 870190096214, of 26/09/2019, p. 12/30
26/85
CBGs (for example, a subset) of TB, and CBG granularity can be configurable.
[0051] With regard to an aspect of eMBB resource punching for the transmission of URLLC data, an indication of the punching can be provided as discussed above. For example, an UE can obtain an eMBB assignment but can also monitor simultaneous URLLC referrals (for example, at each mini-partition boundary) to see if any resources in its allocation are punctured by transmitting URLLC data to other UEs. When such an indication is provided from the base station and the UE detects the indication, both the base station (for example, gNB) and the UE are aware of the affected CBGs due to resource puncture. According to one aspect, such knowledge of the punctured resources and / or affected CBGs can be used to save overhead in uplink signaling, for example, by eliminating or minimizing the need for CBG level ACK / NACK from the UE to the base station, as will now be discussed.
[0052] According to one aspect, several configurations described here support a single bit ACK / NACK for an eMBB TB with CBG level retransmissions. For example, an eMBB UE may receive a TB including a set of CBGs, some of which may be affected / corrupted due to resource puncturing and thus may fail to decode in the UE. In this case, in some configurations, the UE may send a one-bit ACK to the TB. The single bit ACK can indicate that all CBGs / CBs that are not punctured are received. That is, the
Petition 870190096214, of 26/09/2019, p. 12/31
27/85
Single exemplary ACK described here may indicate that all but CBS / CBGs on the punctured resources are well received and / or decoded in the UE. Since the base station and the UE are aware of the CBGs impacted on the punctured resources due to the indication of URLLC (from the base station to the UE), the UE may not need to send CBG level ACK / NACK when only the CBGs corresponding to the punctured resources fail to decode. Thus, by having a configuration in which there is an agreement / understanding between the base station and the UE, a single bit ACK (TB level) can serve a dual purpose, for example, confirming that all CBGs, except those on resources punctured, are successfully decoded, and implicitly / inherently also indicating the CBGs on the punctured resources need to be retransmitted (since the ACK is for everyone except punctured CBGs). In some, but not all, configurations, due to the simultaneous reception of the URLLC indication and the initial transmission of CBGs in the TB, the UE is able to determine which CBGs are affected due to the puncture (for example, based on the punctured resources indicated in the URLLC indication), and may decide not to decode the affected CBGs and proceed to decode the rest of the CBGs in the TB. If the remaining CBGs are successfully decoded, the UE can send the single bit ACK as discussed above. According to one aspect, the single bit ACK can trigger the retransmission of the affected / punctured CBGs from the base station.
[0053] in a second case, when One or more additional CBGs (for example, other than CBGs
Petition 870190096214, of 26/09/2019, p. 12/32
28/85 affected corresponding to the punched resources) fail to decode the UE, the UE can be configured to send a single bit NACK which indicates that at least some of the transmitted CBS / CBGs that are not punctured, are not received / decoded. According to one aspect, in some configurations, such a NACK triggers retransmission of the entire (complete) TB, for example, the same set of CBGs comprising the TB as they were transmitted for the first transmission. In the event that the UE is unable to detect / decode the URLLC indication indicating the punctured resources (which in turn allowed the UE to determine the affected CBGs), the UE can continue to decode the received CBGs and perform CRC to determine decoding as well successful. If one or more CBGs are determined to fail to properly decode, for example, by checking whether CRC for one or more CBGs has failed, the UE may send a single-bit NACK. Again in this case, the base station, upon receiving the NACK, can relay the entire TB.
[0054] According to another aspect, in addition to relaying only the punctured CBGs or the entire TB, depending on whether the UE provides an ACK or NACK, in various configurations, the base station provides a CBG acknowledgment (also referred to as a CBG list) in a relay grant. The retransmission grant may precede the retransmission of a subset of CBGs (for example, associated with the punctured resources) or complete set of CBGs in some configurations. The CBG list may include information from the previous URLLC indication (for example, on an indicator channel) indicating the affected CBGs
Petition 870190096214, of 26/09/2019, p. 12/33
29/85 for puncturing resources to carry URLLC data. Regardless of whether the UE was able to receive the previous URLLC indication, the CBG list may allow the UE to confirm that CBGs (corresponding to the punctured resources) may have been affected in the first transmission. Unlike some other approaches, the information communicated in a CBG list described here is not based on an ACK / NACK from the UE, but on the information transmitted in a previous URLLC indication. For example, the information communicated in a CBG list described here may reflect CBGs from the initial transmission that were punctured by the URLLC data as communicated by the URLLC indication, and do not require explicit CBK level ACK / NACK feedback from the HUH. Many of the aspects discussed above and resources will become more evident, given the illustrations in the figures
4-8 and the discussion below.
[0055] Figure 4 is a drawing 400 that illustrates signal exchange between a base station 402 and a UE 404, in an exemplary communication system that supports the sharing of dynamic resources between URLLC and eMBB data. When dynamic resource sharing can occur between URLLC and eMBB communication, one or more eMBB resources are punctured / avoided for a URLLC transmission. For example, with reference to Figure 4, base station 402 is considered to need to send URLLC data while an eMBB communication is in progress. As dynamic resource sharing between URLLC and eMBB is supported, base station 402 can drill / avoid one or more resources (for example, resources
Petition 870190096214, of 26/09/2019, p. 12/34
30/85 time-frequency) in which eMBB data is encoded, for example, resources for CBGs corresponding to eMBB communication. In the example, the first (I ^o) transmission 410 of base station 402 reports a TB including CBGS 0 to 11. However, corresponding resources CBGS 5 to 7 are partially punched or punctured. Thus, CBGs 5 to 7 carrying eMBB data may be affected and may not be correctly decoded by UE 404. In some configurations, base station 402 may also provide a URLLC 412 indication of the URLLC punch (shown by the diagonal pattern in the affected CBGs) indicating the punctured resources and / or CBGs that are affected. After receiving the indication of URLLC 412, the UE 404 understands that CBGs corresponding to the expected eMBB data on the indicated punctured eMBB resources may be damaged and may fail to decode. As discussed below, after receiving the first 410 transmission, the UE may decide to decode the received CBGs.
[0056] Assuming that the UE 404 receives / detects the indication of URLLC 412, the UE 404 knows that CBGs 5, 6 and 7 are corrupted (due to the puncturing of resources) and will probably fail to decode. UE 404 can continue to decode all CBGs from the received TB, or it can proceed to simply decode non-affected CBGs (for example, CBGs 0, 1, 2, 3, 4, 8, 9, 8, 10, 11). Assuming that all unaffected CBGs (for example, 0-4 and 8-11) are successfully decoded, the
UE can send an ACK 414. As discussed above, according to one aspect of this disclosure, ACK 414 can indicate to base station 402 that all but the CBS / CBGs
Petition 870190096214, of 26/09/2019, p. 12/35
31/85 on the punctured resources, are successfully decoded in UE 404. Then, based on the understanding between base station 402 and UE 404, base station 402 can interpret the ACK as indicating that all CBGs are not punctured / not affected are decoded properly in UE 404. In response to ACK, base station 402 can send a 420 retransmission of CBGs (5, 6 and 7) that were affected due to punctured / partially punctured resources in the first 410 transmission. In various configurations, relaying (Tx 2) 420 and the first transmission 410 correspond to the same HARQ process. That is, retransmission 420 uses the same HARQ process as the first transmission 410. In addition, a new data indicator (NDI) in retransmission 420 is left uninverted, for example, to indicate that the second transmission 420 is a retransmission of a previous (first) transmission. As illustrated, base station 402 can also send a list of CBG 424 (for example, in a relay lease 422), including previous URLLC indication information 412 indicating the affected CBGs (and also indicates the CBGs retransmitted since in this example the CBGs retransmitted the one or more CBGs that were affected by the puncturing of resources). The list of CBG 424 can be, for example, a bitmap, where l's indicate the corresponding CBGs (mapped to CBGs in the first transmission 410) that are affected due to the puncturing of resources. Since the UE 404 knows that an ACK has been transmitted (having received the ACK 414), in some configurations, the UE 404 can interpret the list of CBG 424 to indicate the retransmitted CBGs included in the
Petition 870190096214, of 26/09/2019, p. 12/36
32/85 retransmission (for example, retransmission) 420. The UE 404 can then proceed to decode the retransmitted CBGs 5, 6 and 7 and verify that the decoding is successful, for example, by executing a CRC.
[0057] Figure 5 is a drawing 500 that illustrates another exchange of signaling between the base station and the UE of the communication system of Figure 4 in an exemplary scenario where a retransmission is triggered by a NACK return. In the example illustrated in Figure 5, the first (I ^o) transmission 510 of base station 402 may report a TB including CBGS 0 to 11. Similar to the previous example discussed with respect to Figure 4, the corresponding resources CBGS 5 to 7 may be punctured or partially punctured by base station 402 to send URLLC data and thus UE 404 may not be able to correctly decode CBGs 5, 6 and 7. Base station 042 may also provide a URLLC 512 indication of the URLLC punch. indicating the punctured resources and / or CBGs that are affected. Assuming that the UE 404 receives / detects the URLLC 512 indication, the UE 404 understands that CBGs 5, 6 and 7 corresponding to the indicated punctured eMBB resources can be corrupted and may not be decoded.
[0058] Then, the UE 404 can continue to decode the received 510 transmission. Since the assumption is that the UE 404 received the URLLC 512 indication and thus knows the affected CBGs, the UE 404 may want to try to decode all CBGs received or you can only decode non-punctured CBGs (for example, CBGs 0, 1, 2, 3, 4, 8, 9, 8, 10, 11) that have not been indicated
Petition 870190096214, of 26/09/2019, p. 37/124
33/85 in the URLLC 512 indication as being affected by resource puncture. For the purposes of discussion, consider that, in this example, while CBG 3 504 is not affected due to resource puncturing, CBG 3 504 fails to decode at UE 404, for example, due to erroneous reception, error decoding and / or interference in UE 404. According to one aspect, UE 404 can be configured for NACK of a received transmission in the case when at least one CBG different from the indicated CBGs (in the URLLC 512 indication) as punctured fails to decode. Thus, in this example, UE 404 sends a NACK 514 since UE 404 fails to decode CBG 3 504, which is not included in the group of CBGs (5, 6, 7) on the punctured resources. NACK 514 can indicate to base station 402 that at least one CBG other than the punctured CBGs (CBS / CBGs on the punctured resources) is not successfully decoded in UE 404. Base station 402 can interpret NACK 514 as indicating that some CBGs other than the punctured / affected CBGs failed to decode at UE 404, and can respond in response to NACK, a 520 relay of the full TB, including all CBGs. In various embodiments, the relay (2 Tx) 520 and the first transmission 510 correspond to the same HARQ process and an NDI the relay 520 is not inverted to indicate that the second transmission 520 is a retransmission of a previous transmission (first). As illustrated, base station 402 can also send a list of CBG 524, in a retransmission grant 522, including information from the URLLC indication previously 512 indicating the affected CBGs due to puncturing.
Petition 870190096214, of 26/09/2019, p. 12/38
34/85 resources (and not the entire set of CBGs that are retransmitted). While the complete set of CBGs of the first transmission 510 is retransmitted in retransmission 520, the list of CBG 524 indicates the CBGs that were punctured in the first transmission 510. Thus, in some configurations based on information in the retransmission concession, the UE 404 can decide whether any logarithmic likelihood ratios (LLRs) based on the first transmission 510 can be used for smooth matching, as will be discussed in more detail. Although the CBG 524 list can be communicated in one of several ways, in some configurations the CBG 524 list can be in the form of a bitmap as discussed in the previous example. The UE 404 can then proceed to decode the CBGs of the retransmitted TB and check whether the decoding is successful or not.
[0059] The examples illustrated above in relation to Figures 4-5 assume that the URLLC indication is detected and decoded correctly by the UE 404 and thus the UE 404 knows that CBGs are over resources punctured for the UE 404. In such cases , before, or as part of decoding the CBGs received on a retransmission, the UE 404 can simply override the corresponding LLRs (for example, stored from decoding the CBGs from a first transmission) to the CBGs received on the resources affected and not using the erroneous LLRs (for CBGs over punctured resources) by smooth combination when decoding CBGs from the received retransmission. Overriding erroneous LLRs may be possible because of the URLLC indication that allows UE 404
Petition 870190096214, of 26/09/2019, p. 12/39
35/85 determine the affected CBGs. However, there is a possibility that UE 404 may miss / not detect the URLLC indication and may not know that CBGs are affected due to the puncture. In such cases, there is a greater likelihood of decoding errors in the UE 404 due to the smooth combination of erroneous LLRs corresponding to the CBGs on the punctured resources and the propagation of such errors in future decodings in the UE 404. An example of such a process is discussed in with respect to Figure 6, where UE 404 fails to detect a URLLC indication from base station 402 and uses the CBG list to avoid using erroneous LLRs in future decoding.
[00560] Figure 6 is a drawing 600 illustrating signal exchange between base station 402 and UE 404 and processing in an exemplary scenario where UE 404 fails to receive / detect a preemption indication (for example, URLLC indication). As discussed in the example, in such a case, the UE 404 can use an exemplary CBG list to override erroneous LLRs and reduce the likelihood of future decoding errors. In the example, the first (I ^o) transmission 610 of base station 402 reports a TB including CBGS 0 to 11. The corresponding features CBGS {1, 2, 3} and {5, 6, 7} can be partially punched or punctured through base station 402 to carry URLLC data, and thus the UE 404 may probably be unable to correctly decode the CBGs {1, 2, 3} and {5, 6, 7}. In the example, while base station 402 can provide URLLC indications 611 and 612 of the URLLC punch indicating the punctured resources and / or CBGs that are affected, it is assumed that the UE cannot detect indication 611,
Petition 870190096214, of 26/09/2019, p. 40/124
36/85 for example, due to channel conditions and / or another error in UE 404. Thus, in this case, UE 404 may not be aware that CBGs {1, 2 and 3} are about punctured resources. In such a case, UE 404 can simply assume that only CBGs {5, 6 and 7} are over punctured resources and proceed with decoding the received CBGs. The UE 404 can try to decode all CBGs received or alternatively only the CBGs that are not over the punctured resources based on the received URLLC indication 612. As part of the decoding, the UE 404 can generate LLRs from the CBGs being decoded and store the LLRs for use in potential decoding refinement, for example, by smoothly combining the LLRs into subsequent future decoding, in which case a retransmission of the CBGs is envisaged. If all CBGs received including those on the punctured resources (for example, CBGs {1, 2, 3} and {5, 6, 7}) are decoded, the UE 404 can store the LLRs corresponding to all decoded CBGs. In some configurations, because the UE 404 receives the indication of URLLC 612 and knows that CBGs {5, 6, 7} are over punctured resources, the UE 404 may or may not attempt to decode CBGs {5, 6, 7}, and even if decoded, the UE 404 may not use the LLRs corresponding to the CBGs {5, 6, 7} for smooth combination in future decoding of the retransmitted CBGs since the UE 404 knows that the CBGs {5, 6, 7} are punctured (due to indication 612) and the corresponding LLRs may be unreliable. However, since the UE 404 does not receive the indication 611, the UE 404 can try to decode CBGs {1, 2, 3} and store the LLRs corresponding to CBGs {1, 2, 3} for possible combination
Petition 870190096214, of 26/09/2019, p. 41/124
37/85 LLRs later. In the example, decoding can fail for CBGs {1, 2, 3} and {5, 6, 7} that are (partially or totally) over punctured resources. While UE 404 is aware that CBGs are over punctured resources and therefore can be expected that decoding CBGs {5, 6, 7} may fail, UE 404 may not have similar expectations for CBGs {1, 2, 3}, since UE 404 lost indication 611. Since UE 404 lost indication 611 and does not know that CBGs {1, 2, 3} are over punctured resources, UE 404 can assume that failure decoding CBGs {1, 2, 3} can be a normal failure in decoding CBGs over unpunched resources and therefore can send a NACK 614 to base station 402.
[0061] Upon receiving NACK 614, base station 402 can retransmit all TB in a second transmission (eg retransmission) 620. However, UE 404 does not know that CBGs {1, 2, 3} in the first transmission 610 were over punctured resources (due to the lack of indication 611) and, therefore, the LLRs corresponding to CBGs {1, 2, 3} generated by UE 404, after receiving the first transmission 610 may be erroneous and, thus, unreliable . Thus, UE 404 is unaware that UE 404 should not perform smooth matching for CBGs {1, 2, 3} based on the LLRs previously generated for CBGs {1, 2, 3} which may be erroneous. In the absence of a notification mechanism to indicate to the UE 404 that the previously generated LLRs corresponding to CBGs {1, 2, 3} may be incorrect and must be overridden, the UE 404 may perform a smooth combination of the potentially erroneous LLRs corresponding to the CBGs
Petition 870190096214, of 26/09/2019, p. 42/124
38/85 {1, 2, 3} with newly generated LLRs corresponding to retransmitted CBGs {1, 2, 3}. Such a smooth combination that uses erroneous LLRs can lead to subsequent / future decoding errors and the errors can spread. However, communication of the exemplary CBG list, as described here, remits and avoids the problem by providing the same information that the UE 404 lost earlier due to a failure to detect the URLLC 611 indication as will now be discussed in more detail. detail.
[0062] Referring again to Figure 6, after sending NACK 614, in addition to retransmission monitoring (e.g. retransmission) 620, the UE 404 can also control a CBG / list acknowledgment in a retransmission grant . As illustrated, base station 402 can send (for example, in a retransmission concession 622) the list of CBG 624 including information from previous indication 611 (whose UE 404 lost earlier) and indication from URLLC 612, indicating the affected CBGs due puncturing resources. As shown in drawing 600, the CBG list 624 includes a bitmap with l's in locations corresponding to the affected CBGs that were punctured in the resources in the first transmission 610. From the list of received CBGs 624, UE 404 can determine which CBGs {1, 2, 3} and {5, 6, 7} on resources were punctured in the first transmission 610. In this example, the CBG list 624 also serves as an indication that the previously generated LLRs corresponding to the CBGs indicated in the list of CBG 624 should be canceled / avoided and no smooth combination should be performed for such CBGs. In this way, the UE 404 cancels the
Petition 870190096214, of 26/09/2019, p. 43/124
39/85
Previously generated LLRs (for example, clearing / resetting the LLR buffers) corresponding to CBGs {1, 2, 3} and {5, 6, 7} and does not perform smooth matching for these CBGs. While the UE 404 can perform smooth matching for other remaining CBGs (for example, CBGs 0, 4, 8 to 11) based on the previously generated LLRs (based on CBG decoding from the first 610 transmission) and newly generated LLRs (with based on decoding from retransmission 620), UE 404 can continue to decode retransmitted CBGs {1, 2, 3} and {5, 6, 7], without smooth combination. Suitably, in some configurations, the CBG 624 list can be used by the UE 404 to reset the LLR buffers, for example, to override previously generated incorrect LLRs and to stop smooth matching based on the incorrect LLRs. Thus, in the manner described above, by introducing a list of CBG of the type described here, the propagation of decoding errors can be prevented even when UE 404 fails to detect / receive a URLLC indication.
[0063] From the above discussion, it can be appreciated that, according to several features described here, from the perspective of base station 402, when a retransmission is triggered by a NACK, base station 402 can be configured to retransmit all TB, but you can also send a list of CBG. The retransmission of the TB corresponds to the same HARQ process as the TB in the first transmission, for example, the initial transmission TB 610 and the retransmission TB 620 are associated with the same HARQ process as the TB in the first transmission. In addition, as discussed above, the list of
Petition 870190096214, of 26/09/2019, p. 44/124
40/85
CBG can be included in a retransmission concession and can list CBGs on the punctured resources for
to allow the UE 404 not execute smooth combination i (in LLRs) for the CBGs punctured This aspect is especially more useful we cases in that the UE 404 fails to detect a recommendation in resources Punctured URLLC The
from the base station. When retransmission is triggered by an ACK, base station 402 can be configured to retransmit only the failed CBGs, for example, the CBGs corresponding to the punctured resources. Base station 402 can be further configured to send the retransmission grant including the CBG list which can indicate the failed / punctured CBGs. The CBG list can be based on the indication transmitted in an indication channel, for example, the URLLC indication transmitted to the UE 404.
[0064] Although unlikely, there may be a possibility of a case where the UE reports ACK, but the referral channel is lost by the UE. For example, consider that the UE has lost an indication of punctured resources, but the CBGs received approve decoding, for example, there may be some punctured resources (for example, REs) that affect a CBG but the CBG approves decoding in the UE. While the base station may have provided an indication on the indication channel about the punctured resources, for the purpose of discussion it is assumed that the UE has somehow lost the indication. In such a case, because the base station is aware of the puncturing of resources and under the assumption that the UE has received the indication of punctured resources, the base station upon receiving the ACK from
Petition 870190096214, of 26/09/2019, p. 45/124
41/85
UE can relay failed CBGs in a retransmission (with the understanding that UE is sending an ACK to indicate that all but the punctured CBGs have been successfully decoded). However, if a CBG list is not sent from the base station, the UE may be misled by the content of the retransmission, since the UE lost the indication earlier and from the UE's point of view the CBG decoding approved and there should be no need for retransmission (for example, once the indication is lost and decoding is successful), the UE can consider the case to be a normal transmission, with no resource sharing / puncturing being applied. Thus, it can be appreciated that a CBG list is still useful even in the unlikely event where the UE is unable to detect the indicator channel, successfully decodes the CBGs and reports an ACK, as in a CBG list, the UE may be mistaken for the retransmission content.
[0065] In a configuration, the behavior of the UE, according to the methods described here can be characterized as follows: for a HARQ process, when the UE detects an indication of punctured resources, for example, in an indication channel, the UE can perform decoding of received CBGs and report ACK / NACK based on the result of decoding CBGs not covered in the indication. That is, when a URLLC indication as discussed in relation to Figures 4-6 is received, the UE may determine to send an ACK or NACK based on whether CBGs other than the CBGs indicated to be affected by the puncturing of resources (for example, not covered in the URLLC indication) approved or failed to decode.
Petition 870190096214, of 26/09/2019, p. 46/124
42/85 [0066] In some configurations, when a UE receives a retransmission grant (including the CBG list) following an ACK transmission, the UE can be configured to compare the CBGs indicated in the CBG list with CBGs known to affected by puncturing resources from the indication previously received. If the comparison indicates that the CBGs indicated in the CBG list are the same as the CBGs determined from the previous indication, the UE can continue to decode the retransmitted CBGs without performing a smooth match for the punctured CBGs. If the comparison indicates that the CBGs are not the same (for example, the CBGs listed on the CBG list may be a superset of the CBGs indicated in a previous received indication), the UE can decode the CBGs retransmitted without a smooth match, for example, cancel the previously generated LLRs corresponding to the CBGs indicated in the CBG list and decode without smooth combination of the LLRs for the corresponding CBGs indicated in the CBG list. In cases where a NACK is reported, the base station can relay the entire TB. In some configurations, when a UE receives a retransmission grant (including CBG list) after reporting a NACK, the UE can be configured to reset / override the previously generated LLRs for the CBGs indicated in the CBG list and unscrambled decoding soft. For other remaining CBGs (not indicated in the CBG retransmission), the UE can decode with a smooth combination for best decoding results.
[0067] The previously discussed configurations discussed in connection with Figures 4-6 assume that a
Petition 870190096214, of 26/09/2019, p. 47/124
43/85
ACK or NACK transmitted from UE 404 will be successfully received / decoded at base station 402. For example, in each of the examples discussed with respect to Figures 4-6, assume that single bit ACK / NACK return (414 / 514/614) from UE 404 is correctly received / decoded by base station 402, and there is no misunderstanding between UE 404 and base station 402 with respect to ACK / NACK feedback. However, it is possible that due to an error in receiving / decoding the ACK / NACK return from UE 404, base station 402 may interpret an received ACK as a NACK (referred to as an ACK to NACK error) or interpret a received NACK as an ACK (referred to as a NACK to ACK error). Thus, as it should be appreciated, protection against such errors may be necessary. As will now be discussed, some configurations anticipate the possibility of an error of the type ACK for NACK, or NACK for ACK and provide a mechanism for protection against such errors.
[0068] For better appreciation and understanding of the above concept, first consider an example of an ACK error for NACK illustrated in Figure 7. Figure 7 includes a drawing 700 that illustrates an example in which an ACK error for NACK occurs, for example example, where base station 402 incorrectly interprets a transmitted ACK as a NACK (for example, due to an error reception / decoding at the base station).
[0069] In the example illustrated in Figure 7, the UE 404 may receive a first (I transmission) 710 from the base station 402 of a TB including a set of CBGS 0 to 11. Similar to the example discussed above in
Petition 870190096214, of 26/09/2019, p. 48/124
44/85 with respect to Figure 4, the resources corresponding to CBGs 5 to 7 can be punctured or partially punctured and the base station 402 can provide a URLLC 712 indication of the URLLC punch (shown by the diagonal pattern in the affected CBGs) indicating the punctured resources . Depending on whether the UE 404 receives / detects the URLLC 712 indication, the UE 404 may be able to determine that CBGs 5, 6 and 7 are over the punctured resources and are likely to fail to decode. UE 404 can continue to decode received CBGs. In addition, for this example it is assumed that all unaffected CBGs (eg 0-4 and 8-11) are successfully decoded, so the UE can send an ACK 714 return message to the station base 402. In this example, base station 402 is assumed to receive feedback from ACK 714, but due to an error, base station 042 incorrectly reads feedback received as a NACK instead of the intended ACK. While the intended purpose of the sent return (ACK 714) is to indicate to base station 402 that all but CBS / CBGs on the punctured resources (ie CBGs 5-7) are successfully decoded in UE 404, due to the error , base station 402 reads the return as a NACK and interprets that at least some CBGs other than the punctured CBGs failing to decode at UE 404. Based on the understanding between base station 402 and UE 404, base station 402 can assume that all the set of CBGs (CBGs 0-11) needs to be retransmitted and therefore sends a 720 retransmission including the complete set of CBGs. While base station 402 retransmits the full set of CBGs, the UE 404, knowing that the UE sent a return of ACK 714, can expect to receive only the
Petition 870190096214, of 26/09/2019, p. 49/124
45/85
Failed CBGs in the 720 relay, for example, only 5-7 CBGs.
[0070] Similar to the example discussed above in relation to exemplary Figure 4, base station 402 can also send a relay grant 722, including a list of CBG 724 (based on information from the previous URLLC indication 712), indicating CBGs affected. From the perspective of base station 402, the CBG list 724 is sent in response to / after receiving a NACK (due to incorrect reception / decoding of ACK by base station 402) with the intention of preventing smooth combining, for example, indicating the affected CBGs for which the corresponding LLRs generated by the UE 404 should be overridden / reset by the UE 404. However, from the perspective of the UE 404, the relay grant 722, including the CBG list 724 is received in response to a transmitted ACK 714 return, and the UE 404 can interpret the CBG 724 list as an indication that CBGs are retransmitted in the 720 retransmission since an ACK 714 return has been transmitted from the perspective of the UE 404 (for example , UE 404 can interpret the CBG 724 list based on whether UE 404 transmitted an ACK or a NACK). Thus, due to the ACK error for NACK, a potential misunderstanding / misinterpretation of the CBG list / confirmation of the 722 relay grant may occur. The potential misunderstanding / misinterpretation may be due to the two ways of interpreting the CBG 724 list which depends on a consistent understanding of ACK or NACK on both base station 402 and UE 404.
[0071] To avoid such a mistake / misinterpretation
Petition 870190096214, of 26/09/2019, p. 50/124
46/85 of the CBG list that can be caused by an ACK to NACK error (or NACK to ACK), according to one aspect, an exemplary relay type indicator 726 can be included in the relay grant 722 in addition to the list of CBG 724 as illustrated in Figure 7. 0 Relay type indicator 726 can explicitly indicate whether the relay includes the full set of CBGs or just the failed CBGs, and can be used by UE 404 to correctly interpret what the CBG list 724 intends to indicate. For example, the relay type indicator 726 can be a single bit indicator having a value of 0 or 1, where a 1 can indicate that the complete TB, for example, a complete set of CBGs, is retransmitted on the 720 relay while a 0 may indicate that feathers CBGS flawed (CBGS transmitted over the punctured resources in R Tx 710) are retransmitted in relay 720. according to one aspect, the relay type indicator 726 indicates that the transmission includes the complete set CBGs (for example, the retransmission indicator set to 1), the CBG 724 list should be interpreted to indicate the CBGs (which were probably damaged due to puncturing resources) for which the corresponding LLRs (stored in UE 404) must be canceled / redefined. If the retransmission type indicator indicates that the transmission includes partial CBG retransmission (for example, only punctured CBGs), then the CBG 724 list should be interpreted to indicate the CBGs that are included in the 720 relay. In the current example, the from the relay type indicator 726 (which is defined
Petition 870190096214, of 26/09/2019, p. 51/124
47/85 to 1), the UE 404 can understand that the complete set of CBGs is retransmitted and therefore the CBG 724 list indicates the CBGs for which the previously generated LLRs (from the decoding of I CBGs) ^the Tx 710) must be canceled, for example, the corresponding LLR buffers must be reset, because the CBGs have been punctured and, thus, the previous LLRs are probably incorrect / erroneous. Thus, with the relay type indicator 726 included, on the UE side the interpretation of the CBG 724 list may not only depend (unlike the other configurations discussed with reference to Figures 4-6) on the transmitted return (ACK or NACK) , but rather than what the base station 402 indicates in the relay type indicator 726.
[0072] UE 404 can continue to decode the CBG relay set, but UE 404 can override the previously generated LLRs for CBGs 5, 6 and 7 indicated by the CBG list 724 and not perform smooth matching for CBGs 5, 6, and 7. For other remaining CBGs (for example, 0-4 and 8-11) decoding the retransmitted CBGs may include smooth matching with previously generated LLRs corresponding to the CBGs that were not affected by the puncturing of resources in ^{the first} transmission 710 That is, for the most reliable decoding, the UE 404 can perform a smooth combination of currently computed LLRs (generated as part of decoding the CBGs included in the 720 relay) to CBGs 0-4 and 8-11 and the LLRs previously generated for the same CBGs. For example, smooth combining for CBG 1 may include combining the LLRs previously generated for CBG 1 (from decoding
Petition 870190096214, of 26/09/2019, p. 52/124
48/85 R 1 CBG transmission 710) with the current generated LLRs for 1 CBG (from the decoding first retransmission 720 CBG). The technique of smoothly combining LLRs for reliable decoding is well understood by people skilled in the art and therefore need not be discussed in detail here.
[0073] A case of error from NACK to ACK can be considered in a similar way. 8 includes a drawing 800 illustrating an example where an ACK to NACK error occurs, for example, where base station 402 incorrectly interprets a transmitted NACK as an ACK due to a receive / decode error. In the example, the UE 404 can receive a first (I ^o) 810 transmission from the base station 402 including the set of CBGS 0 to 11. The base station 402 may also send an indication URLLC 812 puncturing URLLC indicating the punctured resources . For the purposes of discussion, consider that indication 812 is correctly received and read by UE 404. UE 404 can proceed to decode received CBGs, and in the example assume that decoding fails for at least one CBG on unpunished resources (for example, resources not indicated by the URLLC 812 indication as punctured resources). That is, at least one non-punctured CBG (for example, CBG 3) fails to decode at UE 404. Thus, according to the aspects discussed above (for example, as discussed with respect to Figure 5), in such a case the UE 404 can send a NACK 814 to indicate that at least one CBG, in addition to the CBGs on the punctured resources, has failed to decode. In the example, assume that base station 402 receives NACK 814, but
Petition 870190096214, of 26/09/2019, p. 53/124
49/85 due to an error, base station 402 incorrectly reads the received feedback as an ACK instead of the intended NACK. Therefore, in contrast to the intended meaning for NACK 814, base station 402 interprets return 814 as an ACK indicating that all CBGs, except CBGs on the punctured resources (i.e. CBGs 5-7), are decoded successfully and therefore assumes that all CBGs of unpunished resources are successfully decoded in UE 404. Thus, due to the NACK-to-ACK error, instead of correctly understanding the need to relay the full set of CBGs, the base station 402 it can be mistaken that only punctured CBGs (CBGs 5-7) need to be retransmitted. With such a misunderstanding, base station 402 may continue to send a retransmission 820, including a subset of CBGs transmitted in the previous transmission 810, for example, only CBGs 5-7. While base station 402 retransmits only CBGs 5-7, UE 4 04, knowing that UE 4 04 sent a NACK 814, may be waiting to receive the full set of CBGs, for example, CBGs 0-11.
[0074] Base station 402 may also send a retransmission grant 822, including a list of CBG 824 (including information from the previous URLLC indication 812), indicating the affected CBGs. Once again, to highlight / reiterate the problem / misunderstanding that can occur in such cases, without the exemplary relay type indicator, it can be noted that from the perspective of base station 402, the list of CBG 824 is sent below / in response to an ACK (due to incorrect reception / decoding of NACK by base station 402) and indicates CBGs
Petition 870190096214, of 26/09/2019, p. 54/124
50/85 that are retransmitted. However, from the perspective of UE 404, the CBG list 824 is received after / in response to transmitted NACK 814 and UE 404 can interpret such a CBG list as an indication that CBGs for corresponding LLRs need to be avoided. while UE 404 expects all CBGs to be retransmitted. Again, similar to the example in Figure 7, it can be seen that without a retransmission type indicator, a misinterpretation of the CBG list (for example, caused due to a NACK to ACK error) can occur. However, by including the relay type indicator 826 in the relay grant 822 in addition to the CBG list 824, such misunderstanding of the CBG list 824 can be similarly avoided, as discussed in connection with the exemplary Figure 7. The relay type indicator 826 in the present example is set to 0 to indicate explicitly that the relay 820 includes only punctured CBGS (CBGS transmitted in punctured resources in R Tx 810). Based on the relay type indicator 826 (set to 0), the UE 404 can determine that only the punctured CBGs are retransmitted on the 820 relay, and the CBG 824 list indicates the CBGs that are included in the 820 relay. In addition, from the list of CBG 824 and based on the previous determination by UE 404 from the previous decoding, UE 404 can determine that the CBG not punctured (CBG 3 in this example) that was unable to decode in the last round (that is, when decode CBGs from I ^to Tx 810) has not been retransmitted. Thus, the UE 404 can report another NACK to the base station 402 to request a
Petition 870190096214, of 26/09/2019, p. 55/124
51/85 full TB retransmission. Although there may be some inefficiency in this approach due to another retransmission, the issue of misunderstanding / misinterpretation of the CBG list is avoided and no errors are propagated.
[0075] Figure 9 is a flow chart 900 of a wireless communication method. The flowchart 900 method can be performed by a base station (e.g., base station 180, 102, 310, 402, apparatus 1102/1102 '). In 902, the base station can transmit a TB to a UE, comprising a set of CBGs including a first subset of CBGs and a second subset of CBGs, where the first subset of CBGs can be transmitted over resources at least partially punctured and the second subset of CBGs can be transmitted over non-punctured resources. The TB can originally be an eMBB TB, that is, a transport block that carries eMBB data. However, in order to communicate delay sensitive URLLC data the base station can drill / avoid some resources that carry CBMBs of eMBB data to carry URLLC data. For example, referring to Figures 4, 5, 7 and 8, base station 402 can transmit a TB including the set of CBGs 0-11, where CBGs 5-7 (for example, first subset) occupy resources that are at least partially punctured (for example, to carry URLLC data), while CBGs 0-4 and 8-11 (second subset) occupy unpunched resources.
[0076] In 903, the base station can transmit an indicator that indicates the resources at least partially punctured for the UE. In some configurations, the base station can send (for example, transmit) the indicator
Petition 870190096214, of 26/09/2019, p. 56/124
52/85 indicating resources at least partially punctured
on one channel in recommendation Per example, in some settings, O indicator can to be transmitted by station base in a PDCCH. In some settings, the
indicator can be transmitted concurrently with an initial transmission of the set of CBGs, or before or after the initial transmission of the set of CBGs. For example, referring to Figure 5, base station 402 can transmit a URLLC 512 indication indicating the resources punctured in an indicator channel. The indicator transmission can allow the UE to receive the first transmission, including the set of CBGs to determine the punctured resources and, in turn, also determine which of the CBGs received may have been corrupted / affected due to the puncturing of the resource.
[0077] In 904, the base station can receive, from the UE, one of an ACK return or a NACK return based on the set of transmitted CBGs. According to one aspect of some configurations, the ACK return can indicate that the CBGs in the second subset of CBGs are successfully decoded. That is, in some configurations, based on an understanding between the base station and the UE, the ACK can be interpreted to indicate that all CBGs, except CBGs that were transmitted over partially punctured resources, were successfully decoded in the UE. In some configurations, the NACK return may indicate that some CBGs in the second subset of CBGs failed to decode in the UE, that is, at least one other CBG other than CBGs that were transmitted over partially punctured resources, failed to decode in the UE.
Petition 870190096214, of 26/09/2019, p. 57/124
53/85
For example, referring to Figure 4-5, base station 402 can receive an HARQ ACK (for example, ACK 414) or a HARQ NACK (for example, NACK 514) from UE 404 based on whether the UE 404 is able to decode all except the CBGs punctured from I ^o Tx (410/510). The base station can receive the ACK / NACK return as ACK 414 when all CBGs in the received set of CBGs, except the first subset of CBGs (on punctured resources), are successfully decoded in the UE and can receive the return as NACK 514 when at least one CBG in the second subset of CBGs (transmitted over unpunished resources) fails to decode in the UE. In some configurations, the ACK / NACK return is a single bit return.
[0078] In 905, the base station can determine whether the received single bit ACK / NACK return is an ACK or a NACK. For example, based on the single bit value, the base station can determine whether the received ACK / NACK return is an ACK or a NACK. For example, if the ACK / NACK bit value is set to 1, the base station may determine that the received ACK / NACK return is an ACK and if it is determined that the ACK / NACK bit value is set to 0 , the base station can determine that the received ACK / NACK return is a NACK.
[0079] In 906, the base can relay station, based on the return of ACK / NACK received a set of CBGS (for example, a complete set of CBGS TB transmitted on I transmission) or the first subset of CBGS (for example, only CBGS who were on resources partially punctured in ^the transmission I). For example, again referring to Figure 4-5, based on
Petition 870190096214, of 26/09/2019, p. 58/124
54/85 if ACK (414) or NACK (514) is received by base station 402, base station 402 can determine whether all TB (for example, set of CBGs 0-11 of the 1st Tx 410/510) it needs to be retransmitted, or a subset of the entire TB (for example, like the first subset of CBGs including CBGs 5-7 that were over punctured resources) needs to be retransmitted. Based on the determination, base station 402 can relay (420) the set of CBGs (for example, 0-11 CBGs when the return received is a NACK) or the first subset of CBGs (for example, CBGs 5-7 when the received return is an ACK). Thus, according to one aspect, in some configurations, the set of CBGs is retransmitted when the received ACK / NACK resource is a NACK, whereas the first subset of CBGs is retransmitted when the received ACK / NACK return is an ACK. As discussed above, from the base station perspective, an incoming ACK can be indicative of successful decoding by the UE of all CBGs, except the first subset of CBGs transmitted over at least partially punctured resources. Likewise, an incoming NACK may indicate that at least one CBG in the second subset of CBGs has failed to decode the UE. In some configurations, the first subset of CBGs can be relayed in a set of resources corresponding to a minipartition of a subframe. The feature set can match a set of OFDM symbols from the subframe minipartition.
[0080] In 908, the base station may transmit, in a retransmission concession, a list of CBG (also referred to here as CBG confirmation), indicating one or more
Petition 870190096214, of 26/09/2019, p. 59/124
55/85 plus CBGs that were transmitted over resources at least partially punctured in the 1st transmission. That is, the CBG list can indicate the first subset of CBGs that were transmitted on the resources at least partially punctured. For example, referring to Figure 7, base station 402 may transmit, in relay grant 722, the CBG list 724 including information, for example, a CBG mask / bitmap 000001110000 indicating the CBGs that were transmitted over resources punctured in the original transmission (1st Tx 710). In some configurations, the CBG list can be based on the information included in a previously transmitted indicator (for example, URLLC 712 indication) indicating the punctured resources. While the transmission operation of the retransmission concession is illustrated in 908 following block 906, in some configurations the retransmission concession can be transmitted concurrently with the retransmission. However, the retransmission grant can be transmitted on a control channel, for example, PDCCH, which is different from the channel that carries the retransmission of one or more CBGs. In some configurations, the retransmission grant may further include a retransmission type indicator (for example, such as indicator 726/826) that indicates whether the retransmission includes the set of CBGs or the first subset of CBGs. Thus, as illustrated in 910, the base station can transmit, in the retransmission grant, a relay type indicator that indicates whether the set of CBGs is retransmitted, or whether the relay includes only the first subset of CBGs.
Petition 870190096214, of 26/09/2019, p. 60/124
56/85
For example, referring again to Figure 7, the relay grant 722 may include the relay type indicator 726, in addition to the CBG list 724. In one aspect, base station 402 may include the relay type indicator 726 in the relay grant 722 to explicitly indicate to the UE 404 whether the associated relay 720 includes the entire TB (e.g., a complete set of CBGs) or only those CBGs that failed to avoid misunderstanding / confusion in the UE. The reasons, various characteristics and / or advantages related to the transmission of a relay type indicator in a relay concession are discussed in more detail in connection with Figures 7-8.
[0081] In various configurations, the base station can transmit (for example, as a unicast or broadcast) the indicator indicating the punctured resources (discussed in connection with the operation of block 903) in an indicator channel, before the retransmission concession. For example, with reference to Figure 4/5, indicator 412/512 can be transmitted concurrently with an initial transmission (for example, at 1st Tx 410/510). In some configurations, the 412/512 indicator can be transmitted by the base station on a PDCCH. In some configurations, where the UE receives the indicator, the ACK return may indicate that all CBGs, except the CBGs transmitted on the punctured resources indicated by the indicator, are successfully decoded. In some of these configurations, the NACK return may indicate that at least one CBG, different from the CBGs that were transmitted over the punctured resources indicated by the indicator, failed to decode.
Petition 870190096214, of 26/09/2019, p. 61/124
57/85 [0082] Figure 10 is a flow chart 1000 of a wireless communication method. Flowchart method 1000 can be performed by a UE (e.g. UE 104, 350, 404, 1150, 1302, 1302 '). In 1002, the UE can receive a set of CBGs including a first subset of CBGs and a second subset of CBGs from a base station, the first subset of CBGs having been transmitted by the base station over at least partially punctured resources (for example , eMBB resources that may have been punctured / avoided to carry URLLC data). For example, referring to Figure 4, UE 404 can receive a TB of the set of CBGs (CBGs 0-11) from base station 402, where a subset (for example, CBGs 5, 6, 7) of the CBGs defined data may have been transmitted over at least partially punctured resources while another subset (eg CBGs 0-4 and 8-11) over non-punctured resources.
[0083] In 1004, the UE may receive an indicator (also referred to as the preemption indicator) indicating resources at least partially punctured from the base station. In some configurations, the indicator indicating the resources at least partially punctured can be received in an indication channel, for example, in the PDCCH. For example, referring to Figure 4/5, UE 404 may receive a URLLC indication 412/512 indicating the punctured resources. The received indicator can allow the UE 404 to determine the punctured resources in which the first subset of CBGs is transmitted by the base station 402 (and received by the UE 404) and, in turn, also determines which CBGs of the received set of CBGs can have
Petition 870190096214, of 26/09/2019, p. 62/124
58/85 have been corrupted / affected due to resource puncture. In other words, the indicator can allow the UE 404 to determine which CBGs correspond to the first subset.
[0084] In 1006, the UE can decode the set of CBGs received from the base station. For example, again with reference to Figure 4/5, UE 404 can decode the received set of CBGs or at least some of the received CBGs and decide whether to send an ACK or a NACK return based on the result of the decoding. For example, in some configurations, each CBG can be decoded independently, for example, separately. In some configurations, the UE can be configured to decode the complete set of CBGs. After or as part of the decryption, the UE can perform a CRC to determine whether the decoding of the CBGs was successful. For example, a decoded CBG for which CRC approves can be considered to be successfully decoded while the CBG for which such a CRC failed can be considered to have failed decoding. As discussed above, since the first subset of CBGs is on punctured / partially punctured resources, decoding the first subset of CBGs is likely to fail.
[0085] In 1008, the UE can transmit, to the base station, an ACK / NACK return based on the decoding. In some configurations, the ACK / NACK return is a single bit indicator. As previously discussed in detail, in some configurations, UE 4 04 can send an ACK return when all CBGs in the received set of CBGs, with the exception of the first
Petition 870190096214, of 26/09/2019, p. 63/124
59/85 subsets of CBGs, are successfully decoded in UE 404. That is, in some configurations, the UE can be configured to send an ACK when all CBGs except CBGs transmitted in the punched resources are successfully decoded. The UE can be further configured to send a NACK return when at least one CBG in the second subset (for example, the subset of CBGs transmitted by the base station on the unpunished resources) of CBGs fails to decode in the UE. For example, as discussed with respect to Figure 5, UE 4 04 can be configured to report a NACK when one or more CBGs from unpunished resources (for example, from CBGs 0-4 and 8-11) fail to decode . In some configurations, the transmission of the ACK / NACK return may be additionally based on the indicator received indicating the resources at least partially punctured. For example, in one configuration, when decoding the received CBGs, the UE can determine based on the indicator (discussed in 1004, supra) whether the CBGs that failed to decode match and / or are the same as the first subset of CBGs that were received from the base station on the punctured / partially punctured resources. If the CBGs that failed to decode are limited to those in the first subset of CBGs, the UE transmits an ACK. If CBGs that failed to decode include one or more additional CBGs, in addition to those over partially punctured resources, the UE can transmit a NACK.
[0086] In 1010, the UE can receive from the base station, based on the transmitted ACK / NACK return,
Petition 870190096214, of 26/09/2019, p. 64/124
60/85 a retransmission of an element of the set of CBGs or the first subset of CBGs. In other words, the UE can either receive a retransmission of the complete set of CBGs or just the first subset of CBGs that were received over punctured resources from the base station for the first transmission from the base station. For example, with reference to Figure 4, it can be appreciated that UE 404 can receive a retransmission only from the subset (for example, CBGs 5-7) of the originally transmitted set of CBGs when an ACK return (for example, ACK 414) is reported by UE 404. Likewise, with reference to Figure 5, UE 404 can receive a retransmission of all TB including the complete set of CBGs (for example, CBGs 0-11) when a NACK return (for example , NACK 514) is reported by UE 404.
[0087] In 1012, the UE may receive, in a retransmission concession, a list of CBG. The CBG list may indicate one or more CBGs, from the set of CBGs, that were received from the base station on resources at least partially punctured in the previous transmission. For example, the CBG list can identify the CBGs of the first subset, that is, the CBGs that were transmitted by the base station over the punctured / partially punctured resources. In addition, in some configurations, the retransmission grant may also include a relay type indicator (for example, the 726/826 indicator). The retransmission type indicator can indicate whether the retransmission includes the set of CBGs or the first subset of CBGs. For example, referring to Figure 7, the UE 404 can receive the
Petition 870190096214, of 26/09/2019, p. 65/124
61/85 CBG list indicating CBGs that were transmitted over punctured / partially punctured resources in I ^o Tx 710. In some configurations, the CBG list may be based on information included in the preemption indicator (for example, URLLC indication 412 / 512/612/712) indicating the punctured resources. For example, the CBG list can identify the CBGs that were transmitted over the punctured resources indicated by the preemption indicator. Because the CBG list is based on the preemption indicator sent previously, the CBG list can, in a way, serve as a confirmation of the UE's understanding of CBGs that have been received on punctured / partially punctured resources. In addition, according to the aspects described, the CBG list can be interpreted by the UE to indicate the CBGs so that previously stored LLRs must be overridden by the UE because the LLRs corresponding to the CBGs on the CBG list can be erroneous / incorrect, for example. example, due to resource puncture. As discussed in more detail with respect to Figures 7-8, according to one aspect, the UE can use the relay type indicator received in the relay grant to correctly interpret the CBG list instead of interpreting the CBG list with based on whether an ACK or NACK was transmitted by the UE which can lead to confusion in some cases. As previously discussed, the use of the retransmission type indicator can allow to avoid / eliminate a misunderstanding / misinterpretation of the received retransmission and the CBG list by the UE. This can be particularly useful in cases of ACK to NACK error or NACK to ACK error as discussed in detail in
Petition 870190096214, of 26/09/2019, p. 66/124
62/85 connection with Figures 7-8.
[0088] In one configuration, in 1014, the UE can determine whether the relay type indicator indicates that the transmission includes the complete set of CBGs (for example, the relay type indicator set to 1) or the first subset of CBGs (for example, the relay type indicator set to 0). Based on the determination in 1014, the operation can proceed along one of the two routes illustrated in the flowchart. If the retransmission type indicator indicates that the transmission includes only the first subset of CBGs, the operation proceeds to block 1016. Since the retransmission type indicator indicates that only the first subset of CBGs is retransmitted, in 1016, the UE can interpret the CBG list to indicate CBGs included in the retransmission, that is, the retransmitted CBGs received in the UE. Then, in 1018, the UE can determine that the CBGs listed in the CBG list correspond to CBGs that failed to decode (executed in 1006). For example, the UE can compare the CBGs identified in the CBG list with the information of CBGs that failed to decode which may be available to the UE based on the stored results of the previously performed decoding. When the retransmitted CBGs are the same as the CBGs that failed to decode (for example, the first subset of CBGs that were transmitted over punctured resources), in 1020 the UE can decode the first retransmitted subset of CBGs without performing smooth matching based on previously stored LLR values for the first subset of CBGs. For example, the UE can
Petition 870190096214, of 26/09/2019, p. 67/124
63/85 resetting the LLR buffers that store the previously generated LLRs corresponding to the first subset of CBGs because the UE knows that the first subset of CBGs was transmitted over punctured resources and the previously generated LLRs can therefore be erroneous. The UE can then proceed to decode the first relayed subset of CBGs. Although the UE can generate LLRs for the first received (retransmitted) subset of CBGs, it cannot smoothly combine the LLRs currently generated with the previously stored LLRs. By avoiding smooth matching based on the LLRs previously stored for the first subset of CBGs (which may be likely to be erroneous due to resource puncturing), the spread of decoding errors can be reduced or eliminated. If decoding (1020) fails (for example, a CRC fails) for one or more CBGs in the first subset of CBGs, the UE can send an ACK again to request retransmission of the first subset of CBGs.
[0089] Referring again to 1014, if the retransmission type indicator indicates that the transmission includes the complete set of CBGs (that is, all CBGs are retransmitted), the operation may move to block 1022. In 1022, the UE can determine, based on the type of retransmission indicator, that the CBG list indicates CBGs for which previously stored LLR values should be overridden. As previously discussed in detail with respect to Figure 7-8, in some configurations, the UE can interpret the CBG list and the content of the retransmission based on the type of indicator.
Petition 870190096214, of 26/09/2019, p. 68/124
64/85 retransmission and not based on whether the retransmission is in response to an ACK or NACK. Because the relay type indicator indicates that the full set of CBGs is retransmitted, the UE can understand that the CBG list indicates the CBGs for which the previously stored LLR values should be overridden by the UE (and not what the retransmission is for. includes). Thus, due to the CBG list indicating the first subset of CBGs transmitted over the partially punctured resources, the UE can redefine the LLR buffers that store the previously generated LLRs corresponding to the first subset of CBGs thereby canceling the previously stored LLRs corresponding to the first subset of CBGs. Then, at 1024, the UE can decode the first retransmitted subset of CBGs without performing smooth matching based on the previously stored LLR values (which are overridden instead, as discussed above) that correspond to the first subset of CBGs. Thus, according to one aspect, such decoding purposefully avoids smooth matching based on the previously stored LLRs corresponding to the first subset of CBGs because the LLRs previously generated for the first subset of CBGs are likely to be erroneous / incorrect due to resource puncturing. Then, in 1026, the UE can decode the second relayed subset of CBGs from the retransmitted set of CBGs with smooth combination based on LLR values previously stored for the second subset of CBGs. Since the second subset of CBGs was over unpunched resources for the first transmission, the LLR values previously stored for
Petition 870190096214, of 26/09/2019, p. 69/124
65/85 the second subset of CBGs (for example, which can be generated by the UE after receiving the second subset of CBGs in the first transmission) are considered to be correct and reliable. Thus, for improved decoding (for example, more accurate and reliable), the UE can decode the second relayed CBGs subset by smoothly combining based on previously stored LLR values for the second CBGs subset. For example, the UE can generate LLRs corresponding to the second relayed subset of CBGs and smoothly combine the LLRs currently generated for the second relayed CBGs subset with the LLR values previously stored for the second CBGs subset and decode the second relayed subset of CBGs based on the combined LLRs.
[0090] If the decoding (1024) of the first relayed CBG subset fails to one or more CBGs of the first subset, the UE can send an ACK again to request the retransmission of the first CBG subset. If decoding (1026) fails for one or more CBGs from the second relayed subset of the CBGs, the UE can send a NACK again to request retransmission of the complete set of CBGs.
[0091] Figure 11 is a conceptual data flow diagram 1100 that illustrates the data flow between different media / components in an example device 1102. Device 1102 can be a base station (for example, such as a base station 102, 180, 310, 402, 1350). Apparatus 1102 may include a receiving component 1104, a determining component 1106, a measuring component
Petition 870190096214, of 26/09/2019, p. 70/124
66/85 relay grant 1108, a relay control component 1109, and a transmission component 1110.
[0092] Transmission component 1110 can be configured to transmit data and / or other control information to one or more external devices, for example, including UE 1150. In some configurations, transmission component 1110 can be configured to transmit , for UE 1150, a TB including a set of CBGs including a first subset of CBGs and a second subset of CBGs, where the first subset of CBGs is transmitted over at least partially punctured resources and the second subset of CBGs is transmitted over non-punctured resources. For example, with reference to Figures 4-5, base station 402 can transmit a TB including a set of 12 CBGs to the UE 404, for example, in an initial transmission 410/510, where the set of CBGs includes a first set of CBGs {5, 6, 7} transmitted on at least partially punctured resources, and a second subset of CBGs {0, 1, 2, 3, 4, 8, 9, 10, 11} transmitted on unpunched resources. In some configurations, the transmission component 1110 can be additionally configured to transmit an indicator indicating the resources at least partially punctured to the UE 1150. In some configurations, the indicator indicating the resources at least partially punctured can be transmitted on a transmission channel. indication, for example, in a control block of a channel, such as PDCCH. For example, with reference to Figure 5 the transmitted indicator indicating the resources at least partially punctured may include the indication of
Petition 870190096214, of 26/09/2019, p. 71/124
67/85
URLLC 512. In some configurations, the 1110 transmission component may include a preemption indicator generator configured to generate the indicator.
[0093] The receiving component 1104 can be configured to receive messages and / or other information from other devices, including, for example, UE 1150. The signals / information received by the receiving component 1104 can be provided to one or more device components 1102 for further processing and use in carrying out various operations according to the methods discussed above, including the flowchart method 900. In some configurations, the receiving component 1104 can receive, from the UE 1150, a return of ACK / NACK based on the transmitted set of CBGs. For example, with reference to Figures 4-5, apparatus 1102 can be base station 402 and via receiving component 1104 an ACK HARQ (for example, ACK 414) or a NACK HARQ (for example, NACK 514) can be received from UE 404, in response to CBGs initially transmitted, for example, based on whether UE 404 is able to decode all CBGs, minus the punctured CBGs of ^{the first} transmission. In some configurations, the receiving component 1104 can process (for example, decode, retrieve, and / or reformat) the received ACK / NACK return received and transmit the processed ACK / NACK return to the determination component 1106. Thus, the receiving component 1104 may include a decoder to decode the received ACK / NACK feedback and other messages received. Determination component 1106 can be configured to determine whether the received ACK / NACK return is an ACK or
Petition 870190096214, of 26/09/2019, p. 72/124
68/85 a NACK. For example, the received ACK / NACK return can be a single bit return and based on the single bit value (for example, 1 or 0), the determination component 1106 can determine whether the received ACK / NACK return is an ACK or a NACK. The determination component 1106 can be further configured to provide the result of the determination of one or more other components, for example, components 1108 and / or 1109 and / or 1110, to allow such components to take action according to the characteristics of the methods disclosed.
[0094] In one configuration, transmission component 1110 alone, in combination with and / or under the control of relay control component 1109, can be additionally configured to relay one of the set of CBGs (for example, a complete set of CBGs of TB transmitted in the initial transmission) or the first subset of CBGs, based on the received ACK / NACK return. The relay grant component 1108 can be configured to generate a relay grant including a list of CBGs (also referred to here as CBG acknowledgment), indicating the first subset of CBGs that were transmitted over at least partially punctured resources. In some configurations, the CBG list may be based on the information included in the previously transmitted indicator (also referred to here as the preemption indicator and / or URLLC indication) that indicates the resources at least partially punctured. In some configurations, the retransmission grant may also include a relay type indicator that indicates whether the set of CBGs is
Petition 870190096214, of 26/09/2019, p. 73/124
69/85 retransmitted, or if the retransmission includes only the first subset of CBGs.
[0095] Transmission component 1110 alone, in combination with and / or under the control of the relay control component 1109, can further be configured to transmit the relay grant including the CBG list indicating the first subset of CBGs that were transmitted in resources at least partially punctured to the UE 1150. The relay control component 1109 can be configured to control the transmission component 1110 and / or elements of device 1102 to perform relay-related operations according to the characteristics of the methods discussed above.
[0096] The device can include additional components that execute each of the blocks of the algorithm mentioned above in the flow chart of Figure 9. As such, each block in the above mentioned flow chart of Figure 9 can be executed by a component and the device can include one or more of these components. The components can be one or more hardware components specifically configured to perform the indicated process / algorithm, implemented by a processor configured to execute the indicated process / algorithm, stored within a computer-readable medium for execution by a processor, or some combination thereof.
[0097] Figure 12 is a diagram 1200 illustrating an example of a hardware implementation for a device 1102 'employing a processing system 1214. The processing system 1214 can be implemented with a
Petition 870190096214, of 26/09/2019, p. 74/124
70/85 bus architecture, generally represented by the 1224 bus. The 1224 bus can include any number of bus and interconnect bridges depending on the specific application of the 1214 processing system and the overall design constraints. The 1224 bus connects several circuits, including one or more processors and / or hardware components, represented by the 1204 processor, the 1104, 1106, 1108, 1109, 1110 components and the computer / memory readable medium 1206. The 1224 bus can also connect several other circuits such as power
timing devices, peripherals, temperature regulators tension, and circuits in management of energy, which are well known at technical, and, therefore, will not be described more forward.
[0098] The processing system 1214 can be coupled to a transceiver 1210. Transceiver 1210 is coupled to one or more antennas 1220. Transceiver 1210 provides a means for communicating with various other devices through a transmission medium. Transceiver 1210 receives a signal from one or more antennas 1220, extracts information from the received signal, and provides the extracted information to processing system 1214, specifically the receiving component 1104. In addition, transceiver 1210 receives information from the processing system 1214, specifically the transmission component 1110, and based on the information received, it generates a signal to be applied to one or more antennas of 1220. The processing system 1214 includes a processor 1204 coupled to a readable medium per computer / memory 1206. The 1204 processor is responsible for general processing,
Petition 870190096214, of 26/09/2019, p. 75/124
71/85 including running software stored on computer-readable medium / memory 1206. The software, when run by processor 1204, causes processing system 1214 to perform the various functions described above for any particular device. The computer-readable medium / memory 1206 can also be used for storing data that is handled by the 1204 processor when running the software. The processing system 1214 additionally includes at least one of the components 1104, 1106, 1108, 1109, and 1110. The components can be software components running on processor 1204, resident / stored in the computer-readable medium / memory 1206, one or more hardware components attached to the 1204 processor, or some combination thereof. Processing system 1214 may be a component of base station 310 and may include memory 376 and / or at least one of the TX 316 processor, the RX 370 processor and the controller / processor 375.
[0099] In one configuration, the device 1102 '/ 1102 for wireless communication includes means for transmitting a TB, comprising a set of CBGs including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs being transmitted over at least partially punctured resources and the second subset of CBGs being transmitted over non-punctured resources. The TB comprising a set of CBGs can be transmitted to a UE. In some configurations, apparatus 1102/1102 'may further include means for receiving an ACK / NACK return based on the set of CBGs transmitted from the UE. In some
Petition 870190096214, of 26/09/2019, p. 76/124
72/85 configurations, apparatus 1102/1102 'may further include means for retransmitting, based on the received ACK / NACK return, one of the set of CBGs or only the first subset of CBGs. In some configurations, the means for retransmitting may be configured to retransmit the first subset of CBGs in a set of resources corresponding to a minipartition of a subframe.
[00100] In some configurations, the transmission means can be additionally configured to transmit, in a retransmission concession, a list of CBGs including information indicating the first subset of CBGs that were transmitted on the resources at least partially punctured. In some configurations, the retransmission grant may also include a retransmission type indicator that indicates whether the set of CBGs is retransmitted, or whether the retransmission includes only the first subset of CBGs. In some configurations, the transmission means can be additionally configured to transmit, to the UE, an indicator that indicates the resources at least partially punctured. In some configurations, the CBG list can be based on information included in the indicator, and the transmission means can be configured to transmit the indicator that indicates resources at least partially punctured before the transmission of the CBG list in the relay grant.
[00101] The aforementioned means can be one or more of the aforementioned components of the device 1102 and / or the processing system 1214 of the device 1102 'configured to perform the functions mentioned by the means
Petition 870190096214, of 26/09/2019, p. 77/124
73/85 above. As described above, processing system 1214 can include processor TX 316, processor RX 370, and controller / processor 375. As such, in one configuration, the aforementioned means may be processor TX 316, processor 370 RX , and the controller / processor 375 configured to perform the functions cited by the aforementioned means.
[00102] Figure 13 is a conceptual data flow diagram 1300 that illustrates the data flow between different media / components in an example 1302 apparatus. The 1302 apparatus may be a UE (for example, such as the UE 104. , 350, 404, 1150). Apparatus 1302 may include a receiving component 1304, a decoding / decoding component 1306, a decoding result determining component 1308, an ACK / NACK return generating component 1310, and a transmitting component 1312.
[00103] Receiving component 1304 can be configured to receive messages and / or other information from other devices, including, for example, base station 1350. The signals / information received by receiving component 1304 can be provided to one or more more components of the device 1302 for further processing and use in carrying out various operations according to the methods discussed above including the flowchart method 1000. In some configurations, the receiving component 1304 receives, from a base station (for example, base station 1350), one TB including a set of CBGs including a first subset of CBGs and a second subset of CBGs from a base station, the
Petition 870190096214, of 26/09/2019, p. 78/124
74/85 first subset of CBGs having been transmitted by the base station on resources at least partially punctured. In some configurations, the receiving component 1304 may also receive an indicator (also referred to as the preemption indicator) indicating resources at least partially punctured from the base station. For example, referring to Figure 4/5, the indicator received may be the indication of URLLC 412/512 indicating the punctured / partially punctured resources.
[00104] In some configurations, the receiving component 1304 may additionally receive a retransmission of an element of the CBG set or the first subset of CBGs (for example, the subset of CBGs that were transmitted in punctured / partially punctured resources) from from the base station 1350 from the base station based on an ACK / NACK return transmitted to the base station. In some configurations, the receiving component 1304 may additionally receive a relay grant including a CBG list and a relay type indicator, where the CBG list can indicate the first subset of CBGs that were transmitted by the base station on the resources at least partially punctured (for example, in the first / initial transmission) and the retransmission type indicator can indicate whether the retransmission includes the set of CBGs or the first subset of CBGs.
[00105] The decoding / decoding component 1306 can be configured to decode the data and / or other encrypted information received by the device 1302, including, for example, the
Petition 870190096214, of 26/09/2019, p. 79/124
75/85 set of CBGs (received in the initial transmission), first subset of retransmitted CBGs, and / or complete set of retransmitted CBGs. In some configurations, the decoding component 1306 can be implemented as part of the receiving component 1304. The decoding component 1306 can be configured to determine, for example, based on the decoding result, whether the set of CBGs is successfully decoded or one or more CBGs failed to decode. In some configurations, the decoding component 1306 may include a CRC component to perform a CRC in order to determine whether the CBG has been successfully decoded or not. In some configurations, decoding component 1306 can be configured to generate LLRs for each of the CBGs received (for example, for CBGs in an initial transmission, as well as CBGs received in a retransmission) to be decoded and to store the generated LLRs in buffers corresponding LLR. The determined decoding result information, for example, in relation to CBGs that failed to decode, can be provided to one or more other components (for example, such as the ACK / NACK 1310 return generation component and the component 1312) of the device 1302.
[00106] The determination component 1308 can be configured to determine the resources at least partially punctured (on which the base station 1350 transmitted the first subset of CBGs) based on the received preemption indicator. Determination component 1308 can be further configured to determine which CBGs of the set of CBGs received in the TB
Petition 870190096214, of 26/09/2019, p. 80/124
76/85 correspond to the first subset, and that correspond to the second subset, for example, based on the preemption indicator mapping which of the CBGs are received on the punctured / partially punctured resources indicated by the preemption indicator. The determination component 1308 can be further configured to determine, based on the received retransmission type indicator, whether the received retransmission includes the set of CBGs or the first subset of CBGs as discussed with respect to Figures 7-10. In one configuration, when the retransmission type indicator indicates that the transmission includes the first subset of CBGs only, determination component 1308 can be configured to determine, based on the received relay type indicator, that the CBG list indicates CBGs retransmitted by base station 1350 on retransmission. The determination component 1308 can be further configured to determine whether the CBGs indicated in the CBG list correspond to CBGs that failed to decode, for example, CBGs that failed to decode among the set of CBGs received in the first transmission. For example, the determination component 1308 can be configured to compare the CBGs indicated in the CBG list with the CBGs that are determined to have failed decoding (based on information from decoder 1306), and determine whether the two are the themselves. For example, with reference to Figure 4, the CBG list can indicate CBGs {5, 6. 7} that constitute the first subset of CBGs transmitted over the punctured resources and, in the example, the UE 404 failed to decode CBGs {5, 6 . 7}. In the example, based on such
Petition 870190096214, of 26/09/2019, p. 81/124
77/85 information known to UE 404 from the CBG list and decoding result, it can be determined whether the CBGs indicated in the CBG list correspond to CBGs that failed to decode. The result of determinations performed by the determination component 1308 can be provided for the decoder 1306 and / or other components for later use in carrying out other operations and / or actions. In some configurations, when the retransmission type indicator indicates that the retransmission includes the set of CBGs, the determination component 1308 can be configured to determine that the CBG list indicates CBGs for which the previously stored LLR values should be overridden . The determined information can be provided for the decoder 1306 which can override the LLRs by resetting the LLR buffers.
[00107] In some configurations, decoding component 1306 can be additionally configured to decode the first relayed CBGs subset without performing smooth matching based on previously stored LLR values for the first CBGs subset, for example, in response to the determination that the CBGs indicated in the CBG list correspond to the CBGs that failed to decode. In some configurations, when the retransmission includes the complete set of CBGs, decoding component 1306 can be configured to decode the first relayed CBGs subset without performing smooth matching based on the previously stored LLR values and decoding the second relayed CBGs subset , with smooth combination based on LLR values previously stored for the second
Petition 870190096214, of 26/09/2019, p. 82/124
78/85 subset of CBGs.
[00108] The ACK / NACK return generation component 1310 can be configured to generate an ACK / NACK return based on the decoding result received from the decoding component 1306. For example, the ACK / NACK return generation component 1310 can be configured to generate an ACK when all CBGs in the received set of CBGs, except the first subset of CBGs, are successfully decoded. The ACK / NACK 1310 return generation component can be configured to generate a NACK when at least one CBG in the second subset of CBGs fails to decode in the UE. The generated ACK / NACK feedback can be provided for transmission component 1312 for transmission to base station 1350.
[00109] Transmission component 1312 can be configured to transmit feedback from ACK / NACK (s), user data and / or other information to one or more external devices, for example, including the base station 1350. In some configurations, the transmission component 1312 can be configured to transmit the ACK / NACK return (s) based on the decoding of the received CBGs according to the methods described above. In one configuration, transmission component 1312 can be configured to transmit an ACK return when all CBGs in the received set of CBGs, except the first subset of CBGs, are successfully decoded on device 1302 (for example, by decoder 1306) , for base station 1350. In one configuration, transmission component 1312 can be configured to transmit, to base station 1350, a NACK return when at least
Petition 870190096214, of 26/09/2019, p. 83/124
79/85 a CBG in the second subset of CBGs fails to decode. In some configurations, an ACK / NACK return can be transmitted additionally based on the preemption indicator. The apparatus 1302 can be configured to send (e.g., transmit, via transmission component 1312) additional ACK / NACK feedback based on the result of decoding the retransmission received from the complete set of CBGs or the first subset of CBGs.
[00110] The apparatus may include additional components that execute each of the blocks of the algorithm mentioned above in the flowchart of Figure 10. As such, each block in the aforementioned flowchart of Figure 10 may be executed by a component and the apparatus may include one or more of these components. The components can be one or more hardware components specifically configured to perform the indicated process / algorithm, implemented by a processor configured to execute the indicated process / algorithm, stored within a computer-readable medium for execution by a processor, or some combination thereof.
[00111] Figure 14 is a diagram 1400 that illustrates an example of a hardware implementation for a device 1302 'employing a 1414 processing system. The 1414 processing system can be implemented with a bus architecture, generally represented by the 1424 bus. The 1424 bus can include any number of bus and interconnect bridges, depending on the specific application of the 1414 processing system and the overall design constraints. The 1424 bus connects
Petition 870190096214, of 26/09/2019, p. 84/124
80/85 several circuits, including one or more processors and / or hardware components, represented by processor 1404, components 1304, 1306, 1308, 1310, 1312, and the computer-readable medium / memory 1406. The 1424 bus can also connecting various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore will not be described further.
[00112] The processing system 1414 can be coupled to a transceiver 1410. Transceiver 1410 is coupled to one or more antennas 1420. Transceiver 1410 provides a means for communicating with various other devices through a transmission medium. Transceiver 1410 receives a signal from one or more antennas 1420, extracts information from the received signal, and provides the extracted information to processing system 1414, specifically the receiving component 1304. In addition, transceiver 1410 receives information from the processing system 1414, specifically the transmission component 1312, and based on the information received, it generates a signal to be applied to one or more antennas 1420. The processing system 1414 includes a processor 1404 coupled to a readable medium by computer / memory 1406. Processor 1404 is responsible for general processing, including running software stored in computer-readable medium / memory 1406. The software, when run by processor 1404, causes processing system 1414 to perform the various functions described above for any particular device. The medium readable by
Petition 870190096214, of 26/09/2019, p. 85/124
81/85 computer / memory 1406 can also be used for storing data that is handled by processor 1404 when running software. The processing system 1414 additionally includes at least one of the components 1304, 1306, 1308, 1310, 1312. The components can be software components running on processor 1404, resident / stored in the computer-readable medium / memory 1406, one or more hardware components attached to the 1404 processor, or some combination thereof. The processing system 1414 can be a component of the UE 350 and can include the 360 memory and / or at least one of the TX 368 processor, the RX 356 processor and the 359 controller / processor.
[00113] In one configuration, the 1302 '/ 1302 apparatus for wireless communication may comprise means for decoding a set of CBGs received from a base station, the set of CBGs including a first subset of CBGs and a second subset CBGs, the first subset of CBGs having been transmitted over at least partially punctured resources. Apparatus 1302/1302 'may additionally comprise means for transmitting a confirmation return (ACK) / negative confirmation (NACK) based on decoding to the base station. The 1302/1302 'device can
additionally understand means for to receive an retransmission of a set element in CBGs or the first subset based CBGs at the return in ACK / NACK transmitted. [00114] On some settings, the means for reception are additionally configured for to receive an
Petition 870190096214, of 26/09/2019, p. 86/124
82/85 retransmission concession including a CBG list and a relay type indicator, where the CBG list indicates one or more CBGs from the set of CBGs that were transmitted by the base station over at least partially punctured resources, and the indicator retransmission type indicates whether the retransmission includes the set of CBGs or the first subset of CBGs. In some configurations, the transmission means are configured to transmit ACK feedback when all CBGs in the received CBG set, except the first subset of CBGs, are successfully decoded on the device, and transmit the NACK feedback when at least one CBG in the second subset of CBGs it fails to decode on the device. In some configurations, the receiving means is additionally configured to receive an indicator indicating the resources at least partially punctured, where the indicator can be received before the retransmission concession.
[00115] In some configurations, the retransmission type indicator may indicate that the retransmission includes the first subset of CBGs only. In some of such configurations, the receiving means is configured to receive the first subset of CBGs on retransmission. In some of such configurations, apparatus 1302/1302 'may additionally comprise means for determining, based on the transmission type indicator, that the CBG list indicates CBGs included in the retransmission. The means for determination can be further configured to determine whether the CBGs indicated in the CBG list correspond to CBGs that have failed to decode.
Petition 870190096214, of 26/09/2019, p. 87/124
83/85
In some of these configurations, the means for decoding are additionally configured to decode the first relayed CBGs subset without performing a smooth match based on the logarithmic likelihood ratio (LLR) values previously stored for the first CBGs subset when the CBGs indicated in the CBG list correspond to the CBGs that failed to decode.
[00116] In some configurations, the retransmission type indicator may indicate that the retransmission includes the set of CBGs. In some of such configurations, the receiving medium is configured to receive the set of CBGs on retransmission. In some of such configurations, apparatus 1302/1302 'may additionally comprise means for determining, based on the transmission type indicator, that the CBG list indicates CBGs for which the previously stored LLR values are to be overridden. In some of such configurations, the decoding means are further configured to decode the first relayed CBGs subset without performing smooth matching based on the previously stored LLR values, and decoding the second relayed CBGs subset with smooth matching based on values of LLR previously stored for the second subset of CBGs.
[00117] The aforementioned means can be one or more of the aforementioned components of the apparatus 1302 and / or the processing system 1414 of the apparatus 1302 'configured to perform the functions cited by the aforementioned means. As described above, the
Petition 870190096214, of 26/09/2019, p. 88/124
84/85 processing 1414 may include the TX 368 processor, the RX 356 processor, and the 359 controller / processor. As such, in one configuration, the aforementioned means may be the TX 368 processor, the 356 RX processor, and the controller / processor 359 configured to perform the functions cited by the aforementioned means.
[00118] It is understood that the specific order or hierarchy of blocks in the disclosed processes / flowcharts is an illustration of exemplary approaches. Based on the design preferences, it is understood that the order or hierarchy of specific blocks in the processes / flowcharts can be rearranged. In addition, some blocks can be combined or omitted. The tracking method claims present elements of the various blocks in a sample order, and are not intended to be limited to the specific order or hierarchy presented.
[00119] The previous description is provided to allow any person specialized in the technique to practice the various aspects described here. Various changes to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown here, but the full scope consistent with the language claims must be given, where reference to an element in the singular is not intended to mean one and only one unless specifically so declared, but one or more. The word exemplary is used here to mean serving as an example, case, or illustration. Any aspect described here as
Petition 870190096214, of 26/09/2019, p. 89/124
An exemplary 85/85 should not necessarily be interpreted as preferred or advantageous in relation to other aspects. Unless specifically stated otherwise, the term does not refer to one or more. Combinations such as at least one from A, B, or C, one or more from A, B, or C, at least one from A, B, and C, one or more from A, B, and C, and A, B, C, or any combination thereof include any combination of A, B and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as at least one of A, B , or C, one or more of A, B, or C, at least one of A, B, and C, one or more of A, B, and C, and A, B, C, or any combination thereof, they can be just A, just B, just C, A and B, A and C, B and C, or A and B and C, where any such combinations can contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure, which are known or will later be known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is expressly stated in the claims. The words module, mechanism, element, device, and the like cannot be a substitute for the word means. As such, no element according to the claim is to be interpreted as a more functional means unless the element is expressly recited using the phrase means for.

权利要求:
Claims (16)
[1]
1. Wireless communication method for a base station, comprising:
transmit, to a user equipment (UE), a transport block (TB) including a set of code block groups (CBGs) including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs being transmitted about resources at least partially punctured and the second subset of CBGs being transmitted over non-punctured resources;
receive a negative acknowledgment return (ACK) / ACK (NACK) from the UE based on the set of transmitted CBGs; and retransmit, based on the ACK / NACK feedback received, one of the set of CBGs or just the first subset of CBGs.
[2]
A method according to claim 1, wherein the method additionally comprises:
transmit, in a retransmission concession, a list of CBGs including information indicating the first subset of CBGs that were transmitted on the resources at least partially punctured.
[3]
A method according to claim 2, wherein the retransmission grant additionally includes a retransmission type indicator which indicates whether the set of CBGs is retransmitted or whether retransmission includes only the first subset of CBGs.
[4]
A method according to claim 1, wherein the set of CBGs comprising the TB is retransmitted when the ACK / NACK return received is a NACK; and
Petition 870190096214, of 26/09/2019, p. 91/124
2/16 where only the first subset of CBGs is retransmitted when the ACK / NACK return received is an ACK.
[5]
5. Method according to claim 1, wherein the received ACK / NACK return is an ACK, the ACK indicating that all CBGs in the CBG set except the first subset of CBGs are successfully decoded.
[6]
6. Method according to claim 1, wherein the received ACK / NACK return is a NACK, the NACK indicating that at least one CBG in the second subset of CBGs has failed to decode.
[7]
A method according to claim 2, which further comprises:
transmit to the UE an indicator indicating the resources at least partially punctured; and where the CBG list is based on the information included in the indicator, the indicator having been transmitted to the UE before the CBG list.
[8]
A method according to claim 7, wherein the ACK / NACK return received is either an ACK or a NACK;
where the ACK indicates that all CBGs, except CBGs transmitted over at least partially punctured resources indicated by the indicator, are successfully decoded; and where NACK indicates that at least one CBG, different from the CBGs transmitted on the resources at least partially punctured indicated by the indicator, fails to decode.
[9]
9. The method of claim 2, wherein the CBG list includes a CBG level bitmap that
Petition 870190096214, of 26/09/2019, p. 92/124
3/16 indicates one or more CBGs that were transmitted on the resources at least partially punctured.
10. Method according with The claim 1, in that the first subset of CBGs is retransmitted in one feature set corresponding The a mini-partition in a subframe.11. Method according with The claim 1, in
that the ACK / NACK feedback received is a single bit feedback.
12. Wireless communication device, comprising:
at least one processor attached to a memory and configured to:
transmit to a user equipment (UE) a transport block (TB), including a set of code block groups (CBGs) including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs being transmitted over at least partially punctured resources and the second subset of CBGs being transmitted over non-punctured resources;
receive a negative acknowledgment return (ACK) / ACK (NACK) from the UE based on the set of transmitted CBGs; and retransmit, based on the ACK / NACK feedback received, one of the set of CBGs or the first subset of CBGs.
Apparatus according to claim 12, wherein the at least one processor is additionally configured to transmit, in a concession of
Petition 870190096214, of 26/09/2019, p. 93/124
4/16 retransmission, a list of CBGs including information indicating the first subset of CBGs that were transmitted on the resources at least partially punctured.
An apparatus according to claim 13, wherein the retransmission grant additionally includes a retransmission type indicator which indicates whether the set of CBGs is retransmitted, or whether the retransmission includes only the first subset of CBGs.
An apparatus according to claim 12, wherein the at least one processor is additionally configured to retransmit the set of CBGs comprising the TB when the received ACK / NACK return is a NACK; and wherein the at least one processor is additionally configured to retransmit only the first subset of CBGs when the ACK / NACK feedback received is an ACK.
16. Apparatus according to claim 12, wherein the ACK / NACK return received is an ACK, the ACK indicating that all CBGs in the CBG set except the first CBG subset are successfully decoded.
An apparatus according to claim 12, wherein the received ACK / NACK return is a NACK, the NACK indicating that at least one CBG in the second subset of CBGs has failed to decode.
An apparatus according to claim 13, wherein the at least one processor is additionally configured to transmit, to the UE, an indicator indicating resources at least partially punctured; and
Petition 870190096214, of 26/09/2019, p. 94/124
5/16 where the CBG list is based on the information included in the indicator, the indicator having been transmitted
to EU before the CBG list. 19. Agreement device with The claim 18, in that the ACK / NACK return received is want an ACK or a NACK;where ACK indicates what all CBGs, except
CBGs transmitted over at least partially punctured resources indicated by the indicator, are successfully decoded; and where NACK indicates that at least one CBG, different from the CBGs transmitted on the resources at least partially punctured indicated by the indicator, fails to decode.
An apparatus according to claim 13, wherein the CBG list includes a CBG level bitmap that indicates one or more CBGs that have been transmitted over at least partially punctured resources.
21. Apparatus according to claim 12, wherein the first subset of CBGs is retransmitted in a set of resources corresponding to a minipartition of a subframe.
22. Wireless communication device for a base station, comprising:
means for transmitting a transport block (TB) to a user equipment (UE), including a set of code block groups (CBGs) including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs being transmitted over resources at least partially punctured and the
Petition 870190096214, of 26/09/2019, p. 95/124
6/16 second subset of CBGs being transmitted over non-punctured resources;
means for receiving a negative acknowledgment return (ACK) / ACK (NACK) from the UE based on the transmitted set of CBGs; and means for relaying, based on the received ACK / NACK feedback received, one of the set of CBGs or just the first subset of CBGs.
23. Apparatus according to claim 22, wherein the means for transmission are additionally configured to transmit, in a retransmission concession, a list of CBGs including information indicating the first subset of CBGs that have been transmitted on the resources at least partially punctured.
An apparatus according to claim 23, wherein the retransmission grant additionally includes a retransmission type indicator that indicates whether the set of CBGs is retransmitted, or whether the retransmission includes only the first subset of CBGs.
The apparatus of claim 22, wherein the set of CBGs comprising the TB is retransmitted when the ACK / NACK return received is a NACK; and where only the first subset of CBGs is retransmitted when the ACK / NACK return received is an ACK.
26. Apparatus according to claim 22, wherein the received ACK / NACK return is an ACK, the ACK indicating that all CBGs in the CBG set except the first subset of CBGs are successfully decoded.
Petition 870190096214, of 26/09/2019, p. 96/124
7/16
27. Apparatus according to claim 22, wherein the ACK / NACK return received is a NACK, the NACK indicating that at least one CBG in the second CBGs subset has failed decoding.
An apparatus according to claim 23, wherein the transmission means are additionally configured to transmit, to the UE, an indicator indicating at least partially punctured resources; and where the CBG list is based on the information included in the indicator, the indicator having been transmitted
to EU before the CBG list. 29. Agreement device with The claim 2 8 in that the ACK / NACK return received is want an ACK or a NACK;where ACK indicates what all CBGs, except
CBGs transmitted over at least partially punctured resources indicated by the indicator, are successfully decoded; and where NACK indicates that at least one CBG, different from the CBGs transmitted on the resources at least partially punctured indicated by the indicator, fails to decode.
Apparatus according to claim 23, wherein the CBG list includes a CBG level bitmap that indicates one or more CBGs that have been transmitted over at least partially punctured resources.
31. Apparatus according to claim 22, wherein the means for retransmission are configured to retransmit the first subset of CBGs over a set of resources corresponding to a minipartition of
Petition 870190096214, of 26/09/2019, p. 97/124
8/16 is a subframe.
32. Computer readable medium storing computer executable code, comprising code for:
transmit to a user equipment (UE) a transport block (TB), including a set of code block groups (CBGs) including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs being transmitted over at least partially punctured resources and the second subset of CBGs being transmitted over non-punctured resources;
receive a negative acknowledgment return (ACK) / ACK (NACK) from the UE based on the set of transmitted CBGs; and retransmit, based on the ACK / NACK return received, one of the set of CBGs or just the first
subset of CBGs. 33. Method in communication without thread in one equipment of user (HUH ), which comprises: decode one group set in block in code (CBGs) Received The from a station base, O
set of CBGs including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs having been transmitted over at least partially punctured resources;
transmit a negative acknowledgment return (ACK) / ACK (NACK) to the base station based on decoding; and receive from the base station, based on
Petition 870190096214, of 26/09/2019, p. 98/124
9/16 ACK / NACK return transmitted, a retransmission of an element of the set of CBGs or the first subset of CBGs.
34. The method of claim 33, which further comprises:
receive a relay grant including a CBG list and a relay type indicator, the CBG list indicating one or more CBGs from the set of CBGs that were transmitted by the base station over at least partially punctured resources, the type of relay retransmission indicating whether the retransmission includes the set of CBGs or the first subset of CBGs.
35. The method of claim 33, wherein the transmitted ACK / NACK return is an ACK, wherein the ACK is transmitted when all CBGs in the received set of CBGs, except the first subset of CBGs, are successfully decoded in the UE.
36. The method of claim 33, wherein the transmitted ACK / NACK return is a NACK, wherein the NACK is transmitted when at least one CBG in the second subset of CBGs fails to decode in the UE.
37. The method of claim 34, which further comprises:
receive, before receiving the retransmission concession, an indicator that indicates the resources at least partially punctured.
38. The method of claim 37, wherein the transmission of the ACK / NACK return is additionally based on the received indicator.
39. The method of claim 34, in particular
Petition 870190096214, of 26/09/2019, p. 99/124
[10]
10/16 that the retransmission type indicator indicates that the transmission includes the first subset of CBGs only, the method that additionally comprises:
receive the first subset of CBGs at retransmission; to determine, based on the indicator of type in retransmission, that CBG list indicates CBGs included at retransmission; to determine if CBGs indicated in list of CBG
correspond to CBGs that failed to decode; and decode, in response to the determination that the CBGs indicated in the CBG list correspond to the CBGs that failed to decode, the first relayed subset of CBGs without performing a smooth match based on logarithmic likelihood ratio (LLR) values previously stored for the first subset of CBGs.
40. The method of claim 34, wherein the retransmission type indicator indicates that the transmission includes the set of CBGs, the method which additionally comprises:
receiving the set of CBGs on retransmission;
determine, based on the transmission type indicator, that the CBG list indicates CBGs for which previously stored logarithmic probability ratio (LLR) values should be overridden; and decoding, the first relayed subset of CBGs without performing smooth matching based on the previously stored LLR values; and decode, the second subset retransmitted
Petition 870190096214, of 26/09/2019, p. 100/124
[11]
11/16 of CBGs, with smooth combination based on LLR values previously stored for the second subset of CBGs.
41. User equipment (UE) for wireless communication, comprising:
at least one processor attached to a memory and configured to:
decode a set of code block groups (CBGs) received from a base station, the set of CBGs including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs having been transmitted over resources at least partially punctured;
transmit, to the base station, a negative acknowledgment return (ACK) / ACK (NACK) based on decoding; and receiving from the base station, based on the transmitted ACK / NACK return, a retransmission of an element of the CBG set or the first subset of CBGs.
42. The UE of claim 41, wherein the at least one processor is additionally configured to receive a retransmission grant including a CBG list and a relay type indicator, the CBG list indicating one or more CBGs in the set of CBGs that were transmitted by the base station on resources at least partially punctured, the retransmission type indicator indicating whether the retransmission includes the set of CBGs or the first subset of CBGs.
43. UE according to claim 41, in which the transmitted ACK / NACK return is an ACK, in which the hair
Petition 870190096214, of 26/09/2019, p. 101/124
[12]
12/16 minus a processor is configured to transmit the ACK when all CBGs in the received set of CBGs, except the first subset of CBGs, are successfully decoded in the EU.
44. UE according to claim 41, characterized by the transmitted ACK / NACK return being a NACK, wherein the at least one processor is configured to transmit the NACK when at least one CBG in the second subset of CBGs fails to decode in the UE .
45. The UE of claim 42, wherein the at least one processor is additionally configured to receive an indicator indicating the resources at least partially punctured, which the indicator received prior to the retransmission grant.
46. The UE according to claim 45, wherein the at least one processor is additionally configured to transmit the ACK / NACK feedback further based on the received indicator.
47. UE according to claim 42, wherein the retransmission type indicator indicates that the transmission includes the first subset of CBGs only, wherein the at least one processor is additionally configured to:
receive the first subset of CBGs at retransmission; to determine, based on the indicator of type in retransmission, that CBG list indicates CBGs included at retransmission; to determine if CBGs indicated in list of CBG
correspond to CBGs that failed to decode; and
Petition 870190096214, of 26/09/2019, p. 102/124
[13]
13/16 decode, in response to the determination that the CBGs listed in the CBG list correspond to the CBGs that failed to decode, the first relayed subset of CBGs without performing smooth matching based on previously stored log likelihood ratio (LLR) values for the first subset of CBGs.
48. The UE of claim 42, wherein the retransmission type indicator indicates that the transmission includes the set of CBGs;
where at least one processor is additionally configured to:
receiving the set of CBGs on retransmission;
determine, based on the transmission type indicator, that the CBG list indicates CBGs for which previously stored logarithmic likelihood ratio (LLR) values should be deleted; and decoding the first relayed CBGs subset without performing smooth matching based on the previously stored LLR values, and decoding the second relayed CBGs subset with the smooth matching based on previously stored LLR values for the second CBGs subset.
49. User equipment (UE) for wireless communication, comprising:
means for decoding a set of code block groups (CBGs) received from a base station, the set of CBGs including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs having been transmitted over the
Petition 870190096214, of 26/09/2019, p. 103/124
[14]
14/16 resources at least partially punctured;
means for transmitting a negative ACK / ACK (NACK) based on decoding to the base station (ACK); and means for receiving a retransmission of an element of the CBG set or the first subset of CBGs based on the transmitted ACK / NACK return.
50. The UE of claim 49, wherein the receiving means is further configured to receive a retransmission grant including a CBG list and a relay type indicator, the CBG list indicating one or more CBGs from the set of CBGs that were transmitted by the base station with the resources at least partially punctured, the retransmission type indicator indicating whether the retransmission includes the set of CBGs or the first subset of CBGs.
51. UE according to claim 49, in which the transmitted ACK / NACK return is an ACK, in which the ACK is transmitted when all CBGs in the received set of CBGs, except the first subset of CBGs, are successfully decoded in the UE.
52. UE according to claim 49, wherein the transmitted ACK / NACK return is a NACK, wherein the NACK is transmitted when at least one CBG in the second subset of CBGs fails to decode in the UE.
53. The UE according to claim 50, wherein the receiving means is further configured to receive an indicator indicating the resources at least partially punctured, the indicator being received before the retransmission concession.
Petition 870190096214, of 26/09/2019, p. 104/124
[15]
15/16
54. The UE of claim 53, wherein the transmission of the ACK / NACK return is additionally based on the indicator received.
55. The UE of claim 50, wherein the retransmission type indicator indicates that the transmission includes only the first subset of CBGs;
wherein the receiving means is configured to receive the first subset of CBGs on retransmission;
wherein the UE additionally comprises means for determining, based on the transmission type indicator, that the CBG list indicates CBGs included in the retransmission, where the means for determining are additionally configured to determine whether the CBGs indicated on the CBG list match CBGs that failed to decode; and in which the means for decoding are additionally configured to decode the first relayed CBGs subset without performing smooth matching based on logarithmic likelihood ratio (LLR) values previously stored for the first CBGs subset when the CBGs listed in the CBG list correspond to CBGs that failed to decode.
56. The UE of claim 50, wherein the retransmission type indicator indicates that the transmission includes the set of CBGs;
wherein the receiving means is configured to receive the set of CBGs on retransmission;
wherein the UE additionally comprises means to determine, based on the transmission type indicator, that the CBG list indicates CBGs for which values of
Petition 870190096214, of 26/09/2019, p. 105/124
[16]
16/16 logarithmic likelihood ratio (LLR) previously stored must be canceled; and wherein the means for decoding are further configured to decode the first relayed CBGs subset without performing smooth matching based on previously stored LLR values, and decoding the second relayed CBGs subset with smooth matching based on previously stored LLR values for the second subset of CBGs.
57. Computer readable medium storing computer executable code, comprising code for:
decode a set of code block groups (CBGs) received from a base station, the set of CBGs including a first subset of CBGs and a second subset of CBGs, the first subset of CBGs having been transmitted over resources at least partially punctured;
transmit, to the base station, a negative acknowledgment return (ACK) / ACK (NACK) based on decoding; and receiving from the base station, based on the transmitted ACK / NACK return, a retransmission of an element of the CBG set or the first subset of CBGs.

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112019020124A2|2020-05-05|return for code block group based transmissions

---

KR20190127825A|2019-11-13|Multi-HARQ Methods and Apparatuses for Codeblock Group Based Transmissions

---

KR101976781B1|2019-05-09|Triggering Group acknowledgment / negative acknowledgment or channel state information

---

JP2022033808A|2022-03-02|Triggering group acknowledgment / negative and GACK / channel state information

---

US10721029B2|2020-07-21|Techniques for a hybrid automatic repeat request | mechanism with polar codes

---

US10728925B2|2020-07-28|Extended grant for enhanced component carrier

---

AU2017228737A1|2018-08-16|Narrow-band broadcast/multi-cast design

---

BR112019016639A2|2020-03-31|FRAMEWORK STRUCTURE WITH DUPLEXING BY NARROW BAND TIME DIVISION FOR NARROW BAND COMMUNICATIONS

---

US9948481B1|2018-04-17|Uplink voice and video enhancements

---

BR112021010846A2|2021-08-24|Default beam selection based on a subset of coresets

---

BR112021011052A2|2021-08-31|SIGNALING A SUBSET OF SELECTED CORESETS IN COT

同族专利:

---

公开号 | 公开日

---

US10727987B2|2020-07-28|

---

SG11201907608TA|2019-10-30|

---

WO2018187163A1|2018-10-11|

---

CN110476383A|2019-11-19|

---

JP2020516180A|2020-05-28|

---

EP3607685A1|2020-02-12|

---

KR20190129063A|2019-11-19|

---

TW201842746A|2018-12-01|

---

US20180287745A1|2018-10-04|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

US7517970B2|2003-12-19|2009-04-14|Plexxikon, Inc.|Nucleic acids encoding kinase and phosphatase enzymes, expression vectors and cells containing same|

---

CN101667900B|2008-09-02|2014-11-05|中兴通讯股份有限公司|Method for feeding back HARQ|

---

US11115257B2|2017-03-23|2021-09-07|Huawei Technologies Co., Ltd.|System and method for multiplexing traffic|

---

US10567142B2|2017-03-23|2020-02-18|Apple Inc.|Preemption indicators and code-block-group-based retransmission techniques for multiplexing different services on physical layer frames|MX2019000572A|2017-03-08|2019-07-04|Lg Electronics Inc|Method and apparatus for transmitting and receiving wireless signal in wireless communication system.|

---

US10637615B2|2017-03-30|2020-04-28|Qualcomm Incorporated|Retransmission indication based on an acknowledgement based feedback scheme for wireless communication|

---

WO2018203699A1|2017-05-04|2018-11-08|삼성전자 주식회사|Method and apparatus for data transmission in wireless cellular communication system|

---

JP2019004245A|2017-06-13|2019-01-10|シャープ株式会社|Terminal device, base station device, and communication method|

---

CN110741579A|2017-06-14|2020-01-31|夏普株式会社|Procedure, user equipment and base station for code block group based transmission|

---

US10531443B2|2017-06-15|2020-01-07|Sharp Kabushiki Kaisha|Physical uplink control channelformat adaptation for 5th generationnew radio |

---

CN109639398B|2017-10-09|2021-12-31|华为技术有限公司|Method, device and equipment for sending HARQ-ACK feedback codebook|

---

US10686576B2|2017-11-17|2020-06-16|Qualcomm Incorporated|Techniques and apparatuses for hybrid automatic repeat request acknowledgementfeedback for carrier aggregation in new radio|

---

EP3871350A1|2018-10-23|2021-09-01|Telefonaktiebolaget LM Ericsson |In band signaling of control information and corresponding payload in a physical channel|

---

CN111277370B|2018-12-28|2021-06-18|维沃移动通信有限公司|Transmission method and terminal of uplink control information|

---

EP3966975A1|2019-05-05|2022-03-16|LenovoLimited|Sidelink data packet acknowledgment|

---

US20210068133A1|2019-08-27|2021-03-04|Qualcomm Incorporated|Reception of overlapping physical downlink shared channel communications|

法律状态:
2021-10-19| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

US201762481089P| true| 2017-04-03|2017-04-03|

---

US15/939,165|US10727987B2|2017-04-03|2018-03-28|Feedback for codeblock group based transmissions|

---

PCT/US2018/025229|WO2018187163A1|2017-04-03|2018-03-29|Feedback for codeblock group based transmissions|

---